[
https://issues.apache.org/jira/browse/NIFI-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003968#comment-18003968
]
ASF subversion and git services commented on NIFI-14685:
--------------------------------------------------------
Commit 82f3fc3e63ec81c4179a3ce547e94fb40659ffe5 in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=82f3fc3e63 ]
NIFI-14685 Fixed nested Record object handling in PutElasticsearchRecord
(#10040)
Signed-off-by: David Handermann <[email protected]>
> PutElasticsearchRecord does not correctly handle nested objects within script
> fields
> ------------------------------------------------------------------------------------
>
> Key: NIFI-14685
> URL: https://issues.apache.org/jira/browse/NIFI-14685
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As reported in
> [Slack|https://apachenifi.slack.com/archives/C0L9VCD47/p1750257899047229],
> there is currently a deficiency in the {{PutElasticsearchRecord}} processor's
> handling of the {{Script Record Path}} (and indeeded the {{Dynamic Templates
> Record Path}}) when parsing FlowFile content for driving Elasticsearch
> operations.
> The example provided in the processor's additonal details documentation does
> not work if one uses an {{Infer Schema}} approach in the {{Record Reader}}
> (because the processor calls {{DataTypeUtils.toMap}} which leaves nested JSON
> objects as {{MapRecord}} objects, that JAckson doesn't know how to serialise
> into JSON).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
