Hi Matt, I'm trying to do the same flow, but I need to get the newest file from an FTP server. I tried to set the time to 600000ms but the flow did not work. ${file.lastModifiedTime :toDate("yyyy-MM-dd'T'HH:mm:ssZ") :toNumber() :ge(${now():minus(21600000)}) } How can I get the newest file? Thanks in advance, Thais , Hi Matt! I'm trying to do the same flow, but I need to get the newest file from an FTP. Ho can I do that? I tried to use 600000 (1 minute) but it did not work. ${file.lastModifiedTime :toDate("yyyy-MM-dd'T'HH:mm:ssZ") :toNumber() :ge(${now():minus(6000000)}) } Can you help? ... View more

Great answer like usual ! Just tested your suggestion and it works perfectly ! Thank you so much ! ... View more

@Mehul Shah No problem. At the bottom of every answer is a line that says: Simply click on "Accept" under the answer that helped resolve your issue. As a future note, avoid adding new answers as responses to other answers. Responses should be made as comments so that it is one continuous thread for other users searching for answers to the same issue. Thanks again, Matt ... View more

Hi Matt, Thanks for your reply. I'm using external zk and was using private IP in state.management.xml. Later, when i changed the log level to DEBUG, I got to know that nifi was unable to detect that IP. It was throwing Invalid IP address validation error. Figured out a way of passing public IP since we are going through company's proxy layer. It started working fine. ... View more

Hi @Matt Clarke You nailed it again. The two "old" hosts have Owner : CN=FQDN, etc The new host has Owner: CN=<Shortname>, etc Seems the 2 initial hosts cert have been created by a different script that the one I got. It's not clear where is the problem. I'll check and update the cert where needed. Thanks! ... View more

@Saikrishna Tarapareddy In addition to the answer submitted by @Matt Clarke, ExecuteProcess and ExecuteStreamCommand should work as well. However, you'll want to move the arguments you're passing to kinit to the "Command Arguments" properties in the respective processors. The "Command" property should be set to "kinit" (or "/usr/bin/kinit", the full path to the executable can be provided). The "Command Arguments" property should be set to -k -t /etc/security/keytabs/nifi.keytab nifi/server@domain.COM The "Argument Delimiter" should be set to the space character, since you do not have any embedded spaces in the arguments you're using, or you can use the ";" character, for instance. In that case, "Command Arguments" should be set to -k;-t;/etc/security/keytabs/nifi.keytab;nifi/server@domain.COM ... View more

@Matt Clarke This is what i found in nifi-user.log I had created server certificate, client certificate and a CAcert holding signature of both from tinycert.org. I had mentioned server certificate and CAcert path in nifi.properties and was loading client certificate into my browser. I was using same certificate for both the nifi instances. Like you said I had added the client cert DN under the users but nifi was using server cert DN (which i got to know after seeing the nifi-user.log) for site-to-site authentication. So, i added the server DN under the user and added the same under 'retrieve site-to-site details' policy. Now the issue is fixed. The RPG is now able to establish connection. Thanks, Harshith ... View more

You need to keep the NIFi copy of the data even after writing a copy of it out via the putSFTP? If you need to retain a local copy of the data, route success twice form your putSFTP processor. So you should be able to do this with..... The UpdateAttribute processor can be used to update the filename by adding the following new property to its configuration: The Local copy of your Files remain unchanged down the success relationship to the left. The copy sent down the path to the right will have its content cleared, filename changed, and then sent via another PutSFTP. Thanks, Matt ... View more

Thanks Much. ... View more