[jira] [Commented] (NIFI-7430) LookupRecord change coordinate key for in-place replacement

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

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

Commit af5871460659bd01c641d6bab588bf830860ceac in nifi's branch refs/heads/master from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=af58714 ]

NIFI-7430 - LookupRecord change coordinate key for in-place replacement


> LookupRecord change coordinate key for in-place replacement
> -----------------------------------------------------------
>
>                 Key: NIFI-7430
>                 URL: https://issues.apache.org/jira/browse/NIFI-7430
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>             Fix For: 1.12.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When implementing NIFI-7197, I used the key required by the lookup service as the default coordinate key even though this value is not used when doing in-place replacement. Instead of using the required key, this JIRA is about using the dynamic property key as the coordinate key. This way the lookup service receives
> <property name, value for the record path provided in the dynamic property>
> instead of
> <required key, value for the record path provided in the dynamic property>
> for each replacement to perform.
> Doing this change is super useful when using the ScriptedLookupService, because it gives the information about the field being replaced and allows users to code some custom business logic to update multiple fields in the record in one execution.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)