You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2021/01/19 14:52:00 UTC

[jira] [Commented] (NIFI-8133) PutElasticsearchRecord/ElasticSearchClientService should allow null values to be suppressed

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

Joe Witt commented on NIFI-8133:
--------------------------------

will keep an eye on this and if merged in time for the 1.13 RC we'll take it.

> PutElasticsearchRecord/ElasticSearchClientService  should allow null values to be suppressed
> --------------------------------------------------------------------------------------------
>
>                 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
>          Time Spent: 2h 10m
>  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)