You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/10 02:57:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16738938#comment-16738938 ] 

ASF subversion and git services commented on NIFI-5909:
-------------------------------------------------------

Commit 3e52ae952d05867f3366dc4f796ae193a84b4b2c in nifi's branch refs/heads/master from Alex Savitsky
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3e52ae9 ]

NIFI-5909 added optional settings for date, time, and timestamp formats used to write Records to Elasticsearch

NIFI-5909 added content checks to the unit tests

NIFI-5937 use explicit long value for test dates/times (to not depend on the timezone of test executor)

NIFI-5937 tabs to spaces

Fixing checkstyle violations introduced by https://github.com/apache/nifi/pull/3249 PR)

NIFI-5937 adjusted property descriptions for consistency; limited EL scope to variable registry; added an appropriate validator along with its Maven dependency; moved format initialization to @OnScheduled

NIFI-5909 tabs to spaces

Signed-off-by: Ed <ed...@gmail.com>

This closes #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
>          Time Spent: 1h 50m
>  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)