Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
lguevara
Partner - Creator II
Partner - Creator II

Talend Studio with route use cftp

Hi.

I have an route jobs that have cftp to connect and directory in other server and copy this file using cfile to destination folder. But 

How can I control this since the file in the source is always being copied to the destination? Of course, the file will always exist in the source directory. It should only be copied again if the file in the source is replaced.

lguevara_0-1779823600911.png

 

thanks

 

Labels (3)
3 Replies
Rahul_Kale
Support
Support

Hello lguevara,

Thank you for reaching out to the Qlik community.
 

You can use a file-change control instead of a plain copy.  Below are the best practices that can help you.
 

  1. Compare timestamp/size before copying.
    • Only copy if source file's modified date > the destination file's.
  2. Use a “file watcher” / event rule.
    • Trigger copy only when the file is updated/replaced, not just present.
  3. Rename or archive after copy.
    • After copying, move/rename source (e.g., .processed) so it won’t re-copy.
  4. Use checksum (MD5/SHA).
    • Copy only if the file content has actually changed.

Example logic:-

IF source.last_modified > destination.last_modified   THEN copy file ENDIF

If using scheduler/tools (like Control-M / similar):-

  • Use File Watcher / IN condition with “updated file”.
  • Or use “Do not rerun if unchanged” / “overwrite only if newer” option.

Related documentation (general concepts):-

lguevara
Partner - Creator II
Partner - Creator II
Author

thanks @Rahul_Kale 

And How configure this Compare timestamp/size before copying using cftp or cfile or how implement this file change control.

 

Rahul_Kale
Support
Support

Hello lguevara,
 

cftp / cFile cannot compare timestamp/size by itself → you must implement pre‑check logic (script, route, or job step).