[
https://issues.apache.org/jira/browse/NIFI-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451770#comment-17451770
]
ASF subversion and git services commented on NIFI-8153:
-------------------------------------------------------
Commit d45b23d89f1af203ff9971a96799dbde4e9f7bde in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d45b23d ]
NIFI-8153 custom date/time format properties for PutElasticsearchRecord
Signed-off-by: Joe Gresock <[email protected]>
This closes #5552.
> 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
> Attachments: NiFi-8153.json
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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)
