You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "karthik kadajji (Jira)" <ji...@apache.org> on 2020/02/10 16:38:00 UTC

[jira] [Commented] (NIFI-7013) Recordpath handles timestamp microseconds unexpectedly

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

karthik kadajji commented on NIFI-7013:
---------------------------------------

Hi Adam,
there is nothing unexpected here.. 123456 milliseconds is converted to seconds (which is 123)and hence 2 min is added to the time.. anything past 1000ms would be added to seconds part.  This isnt a bug. please close the ticket

> Recordpath handles timestamp microseconds unexpectedly
> ------------------------------------------------------
>
>                 Key: NIFI-7013
>                 URL: https://issues.apache.org/jira/browse/NIFI-7013
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.10.0, 1.9.2
>            Reporter: Adam Trump
>            Priority: Major
>
> if updateRecord gets a record with a field containing a timestamp-formatted string containing more than 3 decimal places, the leftmost digits are added to the other fields.
>  in a test, updateRecord configured with the property "/timestamp" containing {{format(toDate(/timestamp, "yyyy-MM-dd HH:mm:ss.SSSSSS"), "yy-MMM-dd HH:mm:ss.SSSSSS")}}
>  recieved the record
> id,timestamp
>  1,2019-12-31 13:23:45.123456
>  and updated it to
> id,timestamp
>  1,19-Dec-31 13:25:48.000456



--
This message was sent by Atlassian Jira
(v8.3.4#803005)