[
https://issues.apache.org/jira/browse/NIFI-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yannick Majoros updated NIFI-8958:
----------------------------------
Description:
Following up on NIFI-5081, we have a similar use case: we have a service that
can answer with iso dates ...Z or ...+02:00 .
Java has been supporting ISO 8601 dates for years out of the box, e.g.
ZonedDateTime.pare(). Not having this is quite problematic, and there isn't any
real reason for that anymore.
was:
I've got a Node process that outputs in JSON onto an SQS queue. The dates it
spits out are ISO-8601 dates within a string, which is the normal, default and
best way to do this in JSON.
I tried putting them into MongoDB with PutMongo and they go in as strings,
which is not good ( https://issues.apache.org/jira/browse/NIFI-2079 ).
Gave up on Mongo and tried PostgreSQL...
Figuring I was in Java land I used an esoteric path of GetSQS >
EvaluateJsonPath > UpdateAttribute [
"$\{time:toDate("yyyy-MM-dd'T'HH:mm:ss.SSS'Z'", "GMT") ] > PutSQL to get it
into what I assume is a java.lang.Date, it took me forever to find the
sql.args.N.type's required but for some reason PutSQL does not like
java.util.Dates.
Eventually found the ConvertJSONToSQL processor and this created my SQL for me,
but it doesn't work as it leaves ISO-8601 dates as ISO-8601 dates, which don't
seem to work.
Eventually found this
[https://community.hortonworks.com/questions/84772/putsql-with-date-as-argument.html]
and now I have something working, but I'm using my esoteric GetSQS ->
EvaluateJsonPath -> UpdateAttribute -> PutSQL path again.
Think there should be some documentation around this at least because it's very
non-obvious.
> support for ISO-8601 dates
> --------------------------
>
> Key: NIFI-8958
> URL: https://issues.apache.org/jira/browse/NIFI-8958
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.6.0
> Environment: Ubuntu / Chromeium
> Reporter: Yannick Majoros
> Assignee: Mike Thomsen
> Priority: Minor
>
> Following up on NIFI-5081, we have a similar use case: we have a service
> that can answer with iso dates ...Z or ...+02:00 .
> Java has been supporting ISO 8601 dates for years out of the box, e.g.
> ZonedDateTime.pare(). Not having this is quite problematic, and there isn't
> any real reason for that anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
