You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/18 05:21:01 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=16091126#comment-16091126 ] 

ASF subversion and git services commented on NIFI-2829:
-------------------------------------------------------

Commit a6e94de0bbea99561f0ff788b54db4d9af7e8f6a in nifi's branch refs/heads/master from deonhuang
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a6e94de ]

NIFI-2829 - Add Date and Time Format Support for PutSQL

Fix unit test for Date and Time type time zone problem
Enhance Time type to record milliseconds

This closes #1983.

Signed-off-by: Koji Kawamura <ij...@apache.org>


> 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
>   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)