[
https://issues.apache.org/jira/browse/NIFI-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421757#comment-15421757
]
ASF GitHub Bot commented on NIFI-2576:
--------------------------------------
GitHub user patricker opened a pull request:
https://github.com/apache/nifi/pull/869
NIFI-2576 - PutSQL assumes all Timestamps are provided in Epoch
This change allows for either epoch timestamps or "yyyy-MM-dd hh:mm:ss.SSS"
format; which is the format you get when you call ResultSet.getString on a JDBC
Timestamp column.
Also include a unit test for PutSQL to test both flavors of Timestamps.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/patricker/nifi master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/869.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 #869
----
commit 92eb864c96dc3096c28f6d3a2e13402d7bc0a292
Author: Peter Wicks <[email protected]>
Date: 2016-08-15T16:49:37Z
NIFI-2356
commit b28806b52f0a7c7d35e2713db0495c9af6a55641
Author: Peter Wicks <[email protected]>
Date: 2016-08-15T17:47:46Z
Sync
commit ab0568341c5639998f1a292311a58069ead21e7a
Author: Peter Wicks <[email protected]>
Date: 2016-08-15T21:50:47Z
NIFI-2576
commit 1c7ea31346ce1dbd80b2fd392be1d2f4dfccbabe
Author: Peter Wicks <[email protected]>
Date: 2016-08-15T21:52:45Z
Merge remote-tracking branch 'upstream/master'
commit 4ce80fa69ac8524756818dd6d530954985b430c5
Author: Peter Wicks <[email protected]>
Date: 2016-08-15T22:00:31Z
NIFI-2576
----
> PutSQL assumes all Timestamps are provided in Epoch
> ---------------------------------------------------
>
> Key: NIFI-2576
> URL: https://issues.apache.org/jira/browse/NIFI-2576
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Peter Wicks
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When PutSQL sees a TIMESTAMP data type it assumes that it's being provided as
> a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro
> return timestamps as strings; and thus following the Avro->JSON->JSON To SQL
> Route leads to timestamps as being strings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
