You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Otto Fowler (JIRA)" <ji...@apache.org> on 2018/08/07 17:35:00 UTC
[jira] [Commented] (NIFI-5495) Allow configuration of DateFormat
for Mongo Processors
[ https://issues.apache.org/jira/browse/NIFI-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572022#comment-16572022 ]
Otto Fowler commented on NIFI-5495:
-----------------------------------
I was just pasting the code in here when I refreshed as saw your comment. You beat me to it!
I changed the name of the ticket to match the actual ask. Hope you don't mind.
> Allow configuration of DateFormat for Mongo Processors
> ------------------------------------------------------
>
> Key: NIFI-5495
> URL: https://issues.apache.org/jira/browse/NIFI-5495
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.7.1
> Environment: CentOS 7.5, Java 1.8.0 u172
> Reporter: Ryan Hendrickson
> Priority: Blocker
>
> When using the GetMongo, configured with JSON Type of "Standard JSON", it truncates dates with milliseconds.
>
> I've got a document in Mongo that has a date field that looks like the following:
> {
> ...
> "date" : ISODate("2018-08-06T16:20:10.912Z"
> ...
> }
>
> When GetMongo spits it out, the date comes out as: "2018-08-06T16:20:10Z", noticeably missing the milliseconds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)