What is the desired outcome? Are you trying to have a single merged file that included all 170 input files?
The merger content processor is looking at the incoming connection's queue Everytime it runs. If you run schedule is 0, that means as fast as possible. When it sees file it immediately bins those files. If at that time the bin requirements have been met, the FlowFiles in that bin are merged. You min bin requirement is only 1. So my guess here is that the 170 incoming files did not all land on the incoming queue at the same time, so 13 separate binning actions occurred. If you want only a single output file, adjust the min bin requirements. Thanks, Matt On Dec 8, 2016 2:24 PM, "srini" <[email protected]> wrote: Hi Matt, I updated the the origianl describtion little bit. And here is the MergeContent screenshot. <http://apache-nifi-developer-list.39713.n7.nabble.com/file/ n14171/Screenshot_2016-12-08_13.png> -- View this message in context: http://apache-nifi-developer- list.39713.n7.nabble.com/Help-with-MergeContent-tp14169p14171.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
