[
https://issues.apache.org/jira/browse/NIFI-10129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555206#comment-17555206
]
Joe Witt commented on NIFI-10129:
---------------------------------
[~vadidde] That property is asking for a single attribute to lookup. Did you
see somewhere it is taking a list and would look all of them up? If you want
to correlate on a set of values from attributes you can create such a join
attribute using EL. Same would be true for load balancing on an attribute.
In just checking the code we pull the value for 'correlation attribute name'
from an attribute with the given name and use that as the grouping mechanism.
So it would not do what you're thinking.
If your correlation attribute name is 'attr1, attr2, attr3' we will literally
look for an attribute named "attr1, attr2, attr3"
So put an UpdateAttribute in front of merge if you need to which sets an
attribute named 'correlationattr' for example and its value is a result of an
expression language statement smashing the attribute values together you need.
> MergeRecord does not throws exception if correlationAtttribute is a list of
> attributes
> --------------------------------------------------------------------------------------
>
> Key: NIFI-10129
> URL: https://issues.apache.org/jira/browse/NIFI-10129
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.15.2
> Reporter: davide
> Priority: Major
>
> When I set correlation Attribute Name to a list of attributes no error where
> throws, furthermore the processor does not works as expected.
> For example list we set is attr1,attr2,attr3,attr4.
> I noticed the same behavior on connection setting `Load Balancing` to
> attribute.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
