[jira] [Updated] (NIFI-12124) Add a RenameRecordField processor
[
https://issues.apache.org/jira/browse/NIFI-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-12124:
Fix Version/s: 2.0.0
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add a RenameRecordField processor
> -
>
> Key: NIFI-12124
> URL: https://issues.apache.org/jira/browse/NIFI-12124
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The RemoveRecordField processor that was recently added has made it much
> simpler to remove specific fields from a Record. However, it's still not
> trivial to rename a field. There are multiple ways to achieve this, but none
> of them are straight-forward.
> It should take as its configuration user-defined properties such that the key
> is a RecordPath and the value is a String literal or a Expression Language
> Expression - much like UpdateRecord does when configured with "Replacement
> Value Strategy" = "Literal Value." When evaluating EL, it should expose
> FlowFile attributes as well as {{field.name}} and {{{}field.value{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12124) Add a RenameRecordField processor
[
https://issues.apache.org/jira/browse/NIFI-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-12124:
Fix Version/s: (was: 1.latest)
> Add a RenameRecordField processor
> -
>
> Key: NIFI-12124
> URL: https://issues.apache.org/jira/browse/NIFI-12124
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The RemoveRecordField processor that was recently added has made it much
> simpler to remove specific fields from a Record. However, it's still not
> trivial to rename a field. There are multiple ways to achieve this, but none
> of them are straight-forward.
> It should take as its configuration user-defined properties such that the key
> is a RecordPath and the value is a String literal or a Expression Language
> Expression - much like UpdateRecord does when configured with "Replacement
> Value Strategy" = "Literal Value." When evaluating EL, it should expose
> FlowFile attributes as well as {{field.name}} and {{{}field.value{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12124) Add a RenameRecordField processor
[
https://issues.apache.org/jira/browse/NIFI-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-12124:
--
Fix Version/s: 1.latest
2.latest
Assignee: Mark Payne
Status: Patch Available (was: Open)
> Add a RenameRecordField processor
> -
>
> Key: NIFI-12124
> URL: https://issues.apache.org/jira/browse/NIFI-12124
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The RemoveRecordField processor that was recently added has made it much
> simpler to remove specific fields from a Record. However, it's still not
> trivial to rename a field. There are multiple ways to achieve this, but none
> of them are straight-forward.
> It should take as its configuration user-defined properties such that the key
> is a RecordPath and the value is a String literal or a Expression Language
> Expression - much like UpdateRecord does when configured with "Replacement
> Value Strategy" = "Literal Value." When evaluating EL, it should expose
> FlowFile attributes as well as {{field.name}} and {{{}field.value{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
