[
https://issues.apache.org/jira/browse/NIFI-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743182#comment-17743182
]
Christopher Landwehr commented on NIFI-9784:
--------------------------------------------
The Property Configuration for the Correlation Attribute Name of the
MergeContent Processor is expecting the Property Name of the attribute that the
user/admin is choosing to utilize to correlate the flowfiles for Bin-Packing.
When you utilize the string `${foo}` as the attribute name it's telling the
processor to merge on the literal string of `${foo}`. None of the flowfiles
are being assigned an attribute name/value of `${foo}` therefore the attribute
doesn't exist to correlate with and meets completion strategy of minimum
flowfiles to merge with. If you are wanting this logic to function based on
your uploaded example you would need to change the Correlation Attribute name
from `${foo}` to `foo`.
I recommend that the resolution status to be marked closed.
> MergeContent Process Ignores Case of the Correlation Attribute Resulting in
> Great Hilarity
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-9784
> URL: https://issues.apache.org/jira/browse/NIFI-9784
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.15.3
> Environment: Linux
> Reporter: Matthew
> Priority: Major
> Attachments: MergeContentProcessorTestCase.xml,
> image-2022-03-09-22-26-57-072.png
>
>
> The MergeContent processor ignores the case of the correlation attribute when
> binary packing.
> This results in the grouping together flow files with dissimilar correlation
> attributes.
> Subsequently the correlation attribute is dropped in the merged flowfile as
> they are not actually equal.
> Interestingly, the correlation attribute is dropped regardless of the
> configuration of the Attribute Strategy. I suspect this is also an artifact
> of how case is handled.
> I'm not sure if the priority is Major as there is an obvious workaround
> (force case).
> In any case (waka waka), I've attached a test... case.
> !image-2022-03-09-22-26-57-072.png|width=905,height=829!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
