[
https://issues.apache.org/jira/browse/NIFI-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353815#comment-17353815
]
ASF subversion and git services commented on NIFI-8133:
-------------------------------------------------------
Commit e0a1cb8a01d7f69200b5042ae1c68042098b27b7 in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e0a1cb8 ]
NIFI-8133 Add ability to supress null/empty values in
ElasticSearchClientService for PutElasticsearchRecord output
NIFI-8133 pass null/empty field handling from PutElasticsearchRecord to
ElasticSearchClientImpl
Signed-off-by: Matthew Burgess <[email protected]>
This closes #4755
> PutElasticsearchRecord/ElasticSearchClientService should allow null values
> to optionally be suppressed/output
> --------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8133
> URL: https://issues.apache.org/jira/browse/NIFI-8133
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.11.4
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Major
> Fix For: 1.14.0
>
> Attachments: NIFI-8133.xml, NIFI-8133_(ES7).json
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> The PutElasticsearchRecord (or the related ES client service) should allow
> for null values to be suppressed (like PutElasticsearchHttpRecord) as it's
> not always desirable to have null values for empty fields (which might be
> present in the schema used to read the data in nifi but not populated).
> Likely this will need changes to the configuration of the ObjectMapper used
> by the ES service depending upon user provided settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)