Okay, so apparently, Correlation Attribute Name does not support expression language. Changing, Correlation Attribute Name from ${trigger.type} to trigger.type solved the issue. Thanks still! ... View more

Thanks a lot Matt! This very well clears the merging logic. However, currently I am facing a strange issue. Suppose I have an attribute called 'trigger.type' on the flowfile, which can be 'mouse' or 'keyboard'. Now, I want to merge flowfiles with same 'trigger.type' values so I have the Correlation Attribute Name set to ${trigger.type} However, it's merging flowfiles with different values for this attribute into the same flowfile. I can't comprehent what am I missing here? These are my settings for the 'MergeContent' processor: Merge Strategy Bin-Packing Algorithm Merge Format Binary Concatenation Attribute Strategy Keep Only Common Attributes Correlation Attribute Name ${trigger.type} Metadata Strategy Ignore Metadata Minimum Number of Entries 6000 Maximum Number of Entries 6000 Minimum Group Size 0 B Maximum Group Size No value set Max Bin Age 300 seconds Maximum number of Bins 15 Delimiter Strategy Text Header [ Footer ] Demarcator , Compression Level 1 Keep Path false Tar Modified Time ${file.lastModifiedTime} ... View more

I have a doubt @Matt Clarke Does NiFi always merge the bins after 'Minimum Number of Entries'? If yes, what's the use for 'Maximum Number of Entries'? My doubt originates from the following use case. I have to merge flowfiles based on the following two conditions: A) No. of flowfiles in the bin reaches 6000 B) Bin age crosses 5 min and at least one flowfile in the bin What should be the settings for this case? Thanks! ... View more

Thanks a lot Bryan! I had been pulling my hair out for days now over this. ... View more

Precisely what I needed. Thanks! ... View more