Hi @Roberto Sancho. Any relevant information in ressources manager logs? ... View more

- I don't understand what is the problem with Windows. Do your files contain timestamps in the filename? If yes, you can use regular expression to filter on the filename based on the date. - If you want all files having an extension but with the extension not being equal to .xls or .xlsx, you can use the following regular expression: ^.*\.(?!xls$|xlsx$)[^.]+$ I would recommend you testing your regular expressions on this website : http://regexr.com/ This site provides a "explain tab" giving information regarding the regular expression and how it works. ... View more

Hi @Sean Byrne, If you want to update the filename before updating the file in HDFS, I would suggest using UpdateAttribute to update attribute 'filename' using expression language. If you want to insert the date inside the flow file content, you could use ReplaceText processor which allows you to leverage the expression language and insert the date where you want and with the format you want. Hope this helps. ... View more

I'm using the same as you: Beginning of file. I think the version should not matter on this processor: it didn't change since 5 months. However if you are able to try with the PR mentioned above, it may be worth it. ... View more

Hi @Thierry Vernhet, I've tried to reproduce the issue but when I set the rolling filename pattern, it works as expected. Here are the steps I did: echo "test" >> /tmp/test.log echo "test" >> /tmp/test.log mv /tmp/test.log /tmp/test.log.01 echo "test" >> /tmp/test.log With the rolling filename pattern set to test.log.* The JIRA I raised is regarding the case the property is not set and I submitted a PR for that. But in case the property is not set, at this point I am not able to reproduce the error. Are there specific properties regarding your environment? I could suggest you to turn logging to DEBUG level and check if you have some interesting messages... ... View more

Not sure to understand. If you do the following test: cat ‘record01’ >> /home/wls.log The NiFi Flow Data Provenance is OK. The line ‘record01’ appears. mv /home/wls.log /home/wls.log.01 cat ‘record02’ >> /home/wls.log I believe the parameters should be the following: File to Tail /home/wls.log Rolling Filename Pattern : wls.log.01 Is that what you did? The observation you made are valid because the processor keeps in its state the position of the last read bytes in the tailed file. This is why if the roll over is not detected by the processor, it won't pick up new data or it will but partially (from the last known position). ... View more