[
https://issues.apache.org/jira/browse/NIFI-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092483#comment-16092483
]
Joseph Witt commented on NIFI-2829:
-----------------------------------
[~ijokarumawak] The commit you applied appears to have broken the build.
TestPutSQL.testUsingDateTimeValuesWithFormatAttribute:551
expected:<1012608000000> but was:<1012521600000>
This appears to come from this commit:
https://github.com/apache/nifi/commit/a6e94de0bbea99561f0ff788b54db4d9af7e8f6a
I cannot quite tell what the travis builds though as from the PR
https://github.com/apache/nifi/pull/1983 this information doesn't appear. But
i am pushing a commit to ignore the broken unit test. Please correct the unit
test. And also once we are pushing commits to master we need to be closing the
JIRA and assigning the fix version.
> 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)
