Hi @mayki wogno The first error message was also written by the same error with the second error message. The processor reported the error twice, because it logged an error message when the ListHDFS processor caught the exception, then re-throw it, and NiFi framework caught the exception and logged another error message. When NiFi framework catches an exception thrown by a processor, it yields the processor for the amount of time specified by 'Yield Duration'. Once the processor successfully accesses core-site.xml and hdfs-site.xml, both error messages will be cleared. ... View more

dont do the SCP part. the files will get downloaded from the NCM when the node connects to it. ... View more

Thanks. It is very clear. ... View more

I post the data using following curl command: curl -H "hdfsdir:/Sandbox_Zone/Test/Landing_Zone/TestDir" -H "year:2017" -H "month:07" --data-binary "@client_mandate.csv" http://test:7000/hdfs_push In the ListHttp processor I have specified the following as regex to read headers: hdfsdir|year|month Then I correctly get the attribtues as hdfsdir, year and month ... View more

@mclark Thanks ! ... View more

@Timothy : I got this flow I'm use for testing this curl curl -i -v -F file=@/var/opt/hosting/log/flume/flume-a1.log http://nifi011:10000/contentListener RouteOnAttribute has properties (abc ==> ${filename:contains('flume')} Why flume log not send tu HDFS ? ... View more

thanks, I'll try it and tell you it is ok. ... View more

@Ayub Khan you can grep "ExternalStatu" or "Status" in the log with workflow id. ... View more