You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/10/13 21:04:00 UTC

[jira] [Commented] (NIFI-12124) Add a RenameRecordField processor

    [ https://issues.apache.org/jira/browse/NIFI-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775063#comment-17775063 ] 

ASF subversion and git services commented on NIFI-12124:
--------------------------------------------------------

Commit 3ae0eedee6ae67c48dd59f68752fa728e4355c41 in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3ae0eedee6 ]

NIFI-12124: This closes #7791. Added a new RenameRecordField processor. In testing, also noticed that the Descendant Wildcard operator (//*) and Descendant Field Path Operator (//name, for instance) did not properly account for array of records or map elements, so addressed those concerns.

Signed-off-by: Joseph Witt <jo...@apache.org>


> 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: 0.5h
>  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)