[
https://issues.apache.org/jira/browse/NIFI-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-3866:
------------------------------
Description: In https://issues.apache.org/jira/browse/NIFI-3838 an
UpdateRecord and RecordPath construct is introduced. We should also build a
PartitionRecord processor which will allow format/schema aware partitioning of
record streams along identified matching column values. The matching value
should show up as a FlowFile attribute on a given bundle of records such that
it can be used for merging and other cases later. That also highlights the
value of a need for MergeRecord which is format/schema aware. We can do merge
later on if appropriate. This should all work as well with a LookupRecord
processor which can interact with a controller service to lookup a value found
in a record using RecordPath and then then the value can be turned into a
flowfile attribute, used for routing, or using RecordPath placed back into the
record to replace an existing value or make a new one. (was: In
https://issues.apache.org/jira/browse/NIFI-3838 an UpdateRecord and RecordPath
construct is introduced. We should also build a PartitionRecord processor
which will allow format/schema aware partitioning of record streams along
identified matching column values. The matching value should show up as a
FlowFile attribute on a given bundle of records such that it can be used for
merging and other cases later. That also highlights the value of a need for
MergeRecord which is format/schema aware.)
> Create PartitionRecord processor to compliment UpdateRecord and RecordPath
> --------------------------------------------------------------------------
>
> Key: NIFI-3866
> URL: https://issues.apache.org/jira/browse/NIFI-3866
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Joseph Witt
>
> In https://issues.apache.org/jira/browse/NIFI-3838 an UpdateRecord and
> RecordPath construct is introduced. We should also build a PartitionRecord
> processor which will allow format/schema aware partitioning of record streams
> along identified matching column values. The matching value should show up
> as a FlowFile attribute on a given bundle of records such that it can be used
> for merging and other cases later. That also highlights the value of a need
> for MergeRecord which is format/schema aware. We can do merge later on if
> appropriate. This should all work as well with a LookupRecord processor
> which can interact with a controller service to lookup a value found in a
> record using RecordPath and then then the value can be turned into a flowfile
> attribute, used for routing, or using RecordPath placed back into the record
> to replace an existing value or make a new one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
