You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Ed Berezitsky (JIRA)" <ji...@apache.org> on 2019/01/10 02:59:00 UTC

[jira] [Resolved] (NIFI-5909) PutElasticsearchHttpRecord doesn't allow to customize the timestamp format

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

Ed Berezitsky resolved NIFI-5909.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

This is addressed by PR #3227

> PutElasticsearchHttpRecord doesn't allow to customize the timestamp format
> --------------------------------------------------------------------------
>
>                 Key: NIFI-5909
>                 URL: https://issues.apache.org/jira/browse/NIFI-5909
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.8.0
>            Reporter: Alex Savitsky
>            Assignee: Alex Savitsky
>            Priority: Major
>             Fix For: 1.9.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> All timestamps are sent to Elasticsearch in the "yyyy-MM-dd HH:mm:ss" format, coming from the RecordFieldType.TIMESTAMP.getDefaultFormat(). There's plenty of use cases that call for Elasticsearch data to be presented differently, and the format should be customizable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)