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

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
mra802003
Contributor III
Contributor III

tWaitForFile doesn't work as expected on UNIX

Hi,

I created a simple job using 'tWaitForFile' and 'tFileCopy'. The file watcher is set to run infinitely and iterate every 10 seconds. If matching file arrives in the directory, the file gets copied to destination directory using 'tFileCopy'. This job is working as expected on Windows. 

Upon deploying this job to UNIX env and executing the ".sh" file, the job doesn't even pick the file from the directory. The 'ps' command shows the job is running continuously as expected. Can anyone help in this regard?

 

Thanks

Labels (2)
1 Solution

Accepted Solutions
TRF
Champion II
Champion II

As you have introduced a tInfiniteLoop you may also replace tWaitForFile by tFileExists (if you know the name) or tFileList. You should have the expected result.

View solution in original post

15 Replies
TRF
Champion II
Champion II

Hi,
Something about the permissions for the source/target folder or the file itself?
mra802003
Contributor III
Contributor III
Author

There are no permission issues on either the folder and files. I am placing the file manually in the source directory and then expecting this job to do the rest.

TRF
Champion II
Champion II

Double check the permissions for the target folder.
Also, try to trace the file pathname at the différent steps.
mra802003
Contributor III
Contributor III
Author

I created another job without 'tWaitForFile' component to make sure there's no permission issue. The file gets copied into the target directory successfully.

TRF
Champion II
Champion II

Can you share the component configuration? Maybe a problem with file mask or the source folder path.
Else, perhaps Talend guys will be most inspired.
mra802003
Contributor III
Contributor III
Author

TRF
Champion II
Champion II

Hum... seems to be a $1,000,000 question!

mra802003
Contributor III
Contributor III
Author

Is this something to do with Open Studio Vs Enterprise edition? I read somewhere over web that trigger functionality is available only in Enterprise edition.

TRF
Champion II
Champion II

Based on the documentation there is no limitation for this component https://help.talend.com/reader/hm5FaPiiOP31nUYHph0JwQ/9NaCQViWaqc8tnoxlpM6HA
What you have on the Enterprise edition is the capability to start a job as soon a file is detected.
Maybe Sabrina @xdshi could help on this topic