Multiple <file_order_source> reprocess non-deleted files

Current Situation

• A remote file watching job chain is configured without a file sink node, Thus after processing, files triggering the job chain are not removed by JobScheduler Master. This is a valid configuration, however, it leaves the responsibility to remove incoming files to the users's jobs.
• If incoming files are not removed by the jobs then JobScheduler Master will reprocess the files.

How to reproduce

• Create a remote file watching job chain with single job node.
• Configure two file_order_source directories, where the directory is the same but each file_order_source has different regex.

  <?xml version="1.0" encoding="ISO-8859-1"?>
  <job_chain  title="Watch for incomming files on remote server Load DWH ( LINUX REMOTE AGENT  -   GALADRIEL.SOS)" file_watching_process_class="JUA_LINUX_GALADRIEL_4110" process_class="JUA_LINUX_GALADRIEL_4110" max_orders="10">
      <file_order_source  directory="/home/sos/data/support/landing" regex="^TRX.*\.CSV$"/>
      <file_order_source  directory="/home/sos/data/support/landing" regex="^TRX.*\.DAT$"/>
  
      <job_chain_node  error_state="Error" job="03_load_stage" next_state="Success" state="100"/>
  
      <job_chain_node  state="Success"/>
  
      <job_chain_node  state="Error"/>
  </job_chain>
  
  

• Configure job chain to watch a directory on an agent, create 3 files matching with regular expression triggering the job chain.
• The master JobScheduler will process files again and again.

Desired Behavior

• The JobScheduler Maser should not pick-up already processed files for processing.

Maintainer Notes

• This is not a bug but a misconfiguration. If no file sink node is used then it is up to the user's jobs to remove incoming files.
• We will not modify JobScheduler Master to cope with this misconfiguration.