[
https://issues.apache.org/jira/browse/NIFIREG-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210051#comment-16210051
]
ASF GitHub Bot commented on NIFIREG-38:
---------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/25
NIFIREG-38 Converting milliseconds to seconds in front-end
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry NIFIREG-38
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/25.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #25
----
commit 05d30a25254139acfc589c0af785dcf7021002f1
Author: Bryan Bende <[email protected]>
Date: 2017-10-18T21:12:08Z
NIFIREG-38 Converting milliseconds to seconds in front-end
----
> Incorrect timestamps returned from REST API
> -------------------------------------------
>
> Key: NIFIREG-38
> URL: https://issues.apache.org/jira/browse/NIFIREG-38
> Project: NiFi Registry
> Issue Type: Bug
> Reporter: Bryan Bende
> Assignee: Bryan Bende
>
> It appears that the timestamps returned from the REST API for created and
> modified are not correct and actually contain more digits than the standard
> epoch. This is likely some issue with conversion to and from the database.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
