[
https://issues.apache.org/jira/browse/NIFI-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Wilson updated NIFI-3996:
---------------------------------
Description:
The MergeContent processor currently has two strategies for merging properties.
We have the need to add a third. We could extend the class but there is not an
extension point to do so. Our only current option is to clone and own the
processor, which we would rather not do.
What we need is a "Keep First" (or "Keep Last") implementation which keeps all
the properties using the the first property key/value found.
was:
The MergeContent processor currently has two strategies for merging properties.
We have the need to add a third. We could extend the class but there is not an
extension point to do so. Our only current option is to clone and own the
processor, which we would rather not do.
What we need is a "Keep First" implementation which keeps all the properties
using the the first (or any) property key/value found.
> MergeContent needs more AttributeStrategy implementations.
> ----------------------------------------------------------
>
> Key: NIFI-3996
> URL: https://issues.apache.org/jira/browse/NIFI-3996
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.2.0
> Reporter: Matthew Wilson
> Priority: Minor
> Labels: features
> Attachments: KeepFirstAttributeStrategy.txt
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The MergeContent processor currently has two strategies for merging
> properties. We have the need to add a third. We could extend the class but
> there is not an extension point to do so. Our only current option is to clone
> and own the processor, which we would rather not do.
> What we need is a "Keep First" (or "Keep Last") implementation which keeps
> all the properties using the the first property key/value found.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
