You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jeff Storck (JIRA)" <ji...@apache.org> on 2017/09/22 22:14:00 UTC

[jira] [Commented] (NIFI-2829) PutSQL assumes all Date and Time values are provided in Epoch

    [ https://issues.apache.org/jira/browse/NIFI-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177248#comment-16177248 ] 

Jeff Storck commented on NIFI-2829:
-----------------------------------

Are there any status updates for [PR 2082|https://github.com/apache/nifi/pull/2082]?  Can we get this JIRA closed out?

> PutSQL assumes all Date and Time values are provided in Epoch
> -------------------------------------------------------------
>
>                 Key: NIFI-2829
>                 URL: https://issues.apache.org/jira/browse/NIFI-2829
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Paul Gibeault
>            Assignee: Peter Wicks
>             Fix For: 1.4.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This bug is the same as NIFI-2576 only extended to data types DATE and TIME.
> https://issues.apache.org/jira/browse/NIFI-2576
> When PutSQL sees a DATE or TIME 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 DATES and TIME values as strings; and thus following the Avro->JSON->JSON To SQL Route leads to DATE and TIME fields as being strings.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)