You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Chris Sampson (Jira)" <ji...@apache.org> on 2021/11/25 20:46:00 UTC

[jira] [Assigned] (NIFI-8153) PutElasticsearchRecord does not allow date/timestamp/time formatting of output

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

Chris Sampson reassigned NIFI-8153:
-----------------------------------

    Assignee: Chris Sampson

> PutElasticsearchRecord does not allow date/timestamp/time formatting of output
> ------------------------------------------------------------------------------
>
>                 Key: NIFI-8153
>                 URL: https://issues.apache.org/jira/browse/NIFI-8153
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Chris Sampson
>            Assignee: Chris Sampson
>            Priority: Major
>
> The PutElasticsearchRecord processor cannot re-format date/timestamp/time fields (defined in the Reader's Avro schema) to non-default formats.
> Elasticsearch can be configured to accept many different types of date/time value formats, but the document source being output by NiFi needs to be matched to the required format in Elasticsearch.
> Other Elasticsearch processors do allow such re-formatting (e.g. PutElasticsearchHttpRecord).
> One possible solution would be to set [date formatters in the Jackson ObjectMapper|https://www.baeldung.com/jackson-serialize-dates] used by the ElasticSearchClientServiceImpl controller service, which serialises the data being sent to Elasticsearch. It would be necessary to ensure the same ObjectMapper still worked correctly when reading date fields from Elasticsearch into NiFi Records (e.g. JsonQueryElasticsearch).



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