[ https://issues.apache.org/jira/browse/NIFI-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572005#comment-16572005 ]
Ryan Hendrickson commented on NIFI-5495: ---------------------------------------- Looks like the date is hard-coded to a specific format: [https://github.com/apache/nifi/blob/b1f78d58a6f5250b4f4e6873b03459a8e987407a/nifi-nar-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/java/org/apache/nifi/processors/mongodb/AbstractMongoProcessor.java#L319] I wonder if that could be a configurable property. > GetMongo Truncates Dates > ------------------------ > > 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)