[
https://issues.apache.org/jira/browse/NIFI-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422787#comment-15422787
]
ASF subversion and git services commented on NIFI-2576:
-------------------------------------------------------
Commit b22500d0a322794aa8a3e95b570bb58e6d62d33e in nifi's branch
refs/heads/master from [~patricker]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b22500d ]
NIFI-2576 Allowing PutSQL to use timestamps in epoch or string format
This closes #869.
Signed-off-by: Bryan Bende <[email protected]>
> 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
> Assignee: Bryan Bende
> Fix For: 1.0.0
>
> 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)
