@Mohammad Soori Just to make sure I understand correctly... - The TailFile is producing only 20 output FlowFiles; however, all 500 records are included within those 20 FlowFiles. correct? - With a Run Schedule of 0 secs, the processor will be scheduled toe execute and then scheduled to execute again immediately following completion of last execution. During its execution, it will consume all new lines seen since last execution. There is no configuration option that will force this processor to output a separate FlowFile for each line read from the file being tailed. - You could however feed the output FlowFiles to a splitText processor to split each FlowFile in to a separate FlowFile per line. - Thank you, Matt - When an "Answer" addresses/solves your question, please select "Accept" beneath that answer. This encourages user participation in this forum. ... View more

@Benjamin Bouret - The listHDFS processor does not retrieve the actual content of the files. It produces 0 byte FlowFiles that have metadata about the target content. Any hash you produce on these files will not match what the hash produced on the original source ftp server. - If I am not following above correctly, I am not really clear on exactly where you are performing this second hash. How you plan to compare the two hashes. Manually? - NiFi has guaranteed delivery when it writes data to HDFS. If the transfer fails for any reason the FlowFile is routed to failure. - FetchFTP processor also has handling of failures in retrieving the Content: - This check seems like a lot of overhead that should not be necessary. - Thank you, Matt - When an "Answer" addresses/solves your question, please select "Accept" beneath that answer. This encourages user participation in this forum. ... View more

@Gitanjali Bare - When the NiFi Site-to-Site (S2S) capability was added to NiFi, the input and output ports were designed to allow for the movement of FlowFiles between NiFi process groups. Input and output ports allow for the movement of FlowFile to and from a parent process group. Once a FlowFile is on the "root" process group level, the effective parent would be another NiFi instance. S2S has been around a lot longer then NiFi's multi-tenant authorizations, thus at the time of development every user who could authenticate in to NiFi had access to everywhere on the NiFi canvas. - There is considerable design changes required to change this functionality in NiFi. The following Jira was opened as one suggested approach: https://issues.apache.org/jira/browse/NIFI-2933 - But in any design change, NiFi must consider how that design change will affect existing user during upgrade. The above change type may leave existing users with invalid flows after upgrade requiring potential substantial re-work. - At this time. the only option for NiFi S2S is having your input/output ports at the root canvas level (remote ports). - Another limitation in multi-tenant NiFi installations is authorized access to these remote input/output ports. The dataflows built by authenticated users do not execute as those users. All flows are executed as the NiFI service user. This means when NiFi A uses S2S to send/retrieve FlowFiles from NiFi B, the servers themselves are being authenticated and authorized in that connection. This means that once NiFI A has been authorized to see X number of remote ports on NiFi B, all users on NiFi A who add a Remote Process Group (RPG) pointing at NiFI B will be able to see and transfer FlowFiles to/from all those Remote ports. - Thank you, Matt - If you found this Answer addressed your original question, please take a moment to login and click "Accept" below the answer. ... View more

@umang s The following NiFi Expression Language statement will return "true" if a match is found: ${anyDelineatedValue("${temp_array}", ","):contains("${category}")} - Thanks, Matt - If you found this Answer addressed your original question, please take a moment to login and click "Accept" below the answer. ... View more