@SaiKumar Akula The same flow above will still work for you except swap out the GenerateFlowFile processor for a GetFile processor. Simply set a "run schedule" for how often you want the GetFile to read the source file and change "Keep Source File" property to true. Every time the processor executes it will read the source text file and it can be passed to the splitText processor in above flow and so on... As long as you don't change the source file's filename, you can edit whenever you want to add new lines or remove URL lines. - - Thanks, Matt ... View more

@Jan Can we keep each post in community.hortonworks.com to a single question? The above is no longer an TLS handshake issue. It is an authorization issue. Please start a new question for this topic. Accepting an answer for this question will close this thread. Thank you, Matt ... View more

@Matt Clarke I was putting the "${schema.fingerprint}" within the MergeContent processor. That is likely the issue I am facing here. Thanks for the feedback. Also, thank you for the explanation about the thread pool and cluster info. I will take that into consideration as I move forward. Appreicate the tips! Chris ... View more

@Matt Clarke Thanks a lot appreciate your help ... View more

Thanks Matt and Anish. It helped me a lot today 🙂 ... View more

After you create multiple input ports in the NiFi, when you link your processor with your RPG, it will promote for you to choose which input port to use with selection list "to input". ... View more

@Mohamed Hossam I think you are missing space in search value property. Use the below regex in search value property ^(.*?) (.*?) IP (.*?) > (.*?) .*$ (or) ([^\s]+)\s([^\s]+)\sIP\s(.*)\s>\s([^\s]+).* Use any of the above regex's. Config:- ... View more

@Lanic - With release of Apache NiFi 1.7 and HDF 3.2 in mid 2018, the ability in terminate threads still executing on a processor that is in a state of "stopping" is now possible. After changing state of processor from start to stop, you will see processor display red square. You should give the running threads an opportunity to complete their execution. If it appears the processor is just not going to stop (hung threads) you can right click on the processor and select "Terminate" from the context menu displayed as follows: ... View more

@Jose Paul - A bin would be eligible for merge with only 1 FlowFile in it since you set minEntries to 1. - When the Processor get scheduled to execute (based on configured run schedule and scheduling strategy), It will look at one of possible many incoming connections and look at only the queued FlowFile at that exact moment in time. It will then bin those FlowFiles based on configuration. So it multiple FlowFiles happen to exist in that connection with sam filename attribute value, they will be placed in same bin. At completion of of placing those FlowFiles in bins, the bins are evaluated if they are eligible to be merged. In your case since minEntries is 1 all bins with 1 or more FlowFiles would be merged. - If you run schedule is set to run as fast as possible (Timer Driven with run schedule of 0 sec), it may be reading the inbound connection so fast that it only contains 1 or just a few FlowFiles per execution. - The other scenario is an inbound connection with over 500 queued FlowFiles at time of execution. If we assume there are more than 500 FlowFiles with unique values assigned to the filename attribute, each would end up be placed in new bin (correlation attribute config). As soon as bin 500 has a FlowFile assigned to it and MergeContent tries to bin unique filename number 501, it has no available bins left so it forces the merging of the oldest bin to free a bin. - Thank you, Matt ... View more