[ 
https://issues.apache.org/jira/browse/NIFI-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Molnar updated NIFI-9545:
-------------------------------
    Attachment: screenshot_4651.png

> LookUpRecord's Record Update Strategy example is not working
> ------------------------------------------------------------
>
>                 Key: NIFI-9545
>                 URL: https://issues.apache.org/jira/browse/NIFI-9545
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.15.0
>         Environment: apache/nifi:1.15.0 official docker image
>            Reporter: Peter Molnar
>            Assignee: Pierre Villard
>            Priority: Major
>             Fix For: 1.16.0
>
>         Attachments: LookUpRecord_empty_array_data_issue.xml, 
> LookUpRecord_key_name_issue.xml, image-2022-01-06-15-56-49-217.png, 
> image-2022-01-06-15-58-08-315.png, screenshot_4647.png, screenshot_4648.png, 
> screenshot_4649.png, screenshot_4650.png, screenshot_4651.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I tried to use LookUpRecord as described in the "Record Update Strategy - 
> Replace Existing Values" section here 
> [https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.15.0/org.apache.nifi.processors.standard.LookupRecord/additionalDetails.html]
> I created a SImpleKeyValue Lookup service with the following values:
>  * FR => France
>  * CA => Canada
> I created a generate flow file processor with the mentioned JSON input.
> I configured LookUpRecord as follows:
> !image-2022-01-06-15-56-49-217.png!
> Once LookUpRecord is executed, I see the following error message:
> !image-2022-01-06-15-58-08-315.png!
>  
> Practically it looks to me that most of the LookUpServices provided with NiFi 
> uses hard coded "key" as the name of the key. I am not sure how a key called 
> "region" is supposed to work with Simple Key Value Lookup Service.
>  
> Please find enclosed a template for reproducing the problem.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to