[
https://issues.apache.org/jira/browse/NIFI-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073114#comment-16073114
]
Joseph Witt commented on NIFI-4148:
-----------------------------------
The processor simply partitions a given stream of records into groupings of
matching recordpath results.
If a given recordpath finds no entry in a given record then it will be grouped
with other records that also do not have a finding.
It isn't about matching versus not matching. Simply grouping.
You can use the attributes of the resulting flowfiles if you need to further
route. Alternatively you could precede this processor with a QueryRecord
processor to select only those records of interest (matches).
UpdateRecord appears to only have success and failure. Perhaps you were
referring to LookupRecord which offers either success/failure or match/no match
optionally based on configuration.
> PartitionRecord odd relationship approach
> -----------------------------------------
>
> Key: NIFI-4148
> URL: https://issues.apache.org/jira/browse/NIFI-4148
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Andre F de Miranda
>
> PartitionRecord currently uses a single "success" relationship to route
> residual flowfiles with both the "desired data" (i.e. data that has been
> matched against a particular dynamic property) and the difference between the
> original flowfile and the desired subset.
> Ideally PartitionRecord should behave like UpdateRecord and split the data
> between the desired data (match) and the unmatched data.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
