[
https://issues.apache.org/jira/browse/SQOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236886#comment-14236886
]
Veena Basavaraj commented on SQOOP-1845:
----------------------------------------
Also, this is a different issue altogether, we should get the current patch in
and have another ticket and much broader discussion around this on how we can
handle this case. Intermediate formats relying on another library have such
pitfalls. I am pretty sure this would have gone unnoticed unless I started to
add these test cases.!
> Make DateTime Column type support datetime with and without timezone (Unit
> test failed due to different timezone)
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SQOOP-1845
> URL: https://issues.apache.org/jira/browse/SQOOP-1845
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Richard
> Assignee: Veena Basavaraj
> Attachments: SQOOP-1845.patch, SQOOP-1845.patch
>
>
> test testDateTimeISO8601Alternative in TestCSVIntermediateDataFormat
> {code}
> assertEquals("2014-10-01T12:00:00.000-07:00",
> dataFormat.getObjectData()[0].toString());
> {code}
> failed with such error message:
> {code}
> org.junit.ComparisonFailure:
> Expected :2014-10-01T12:00:00.000-07:00
> Actual :2014-10-01T12:00:00.000+08:00
> {code}
> seems issue of a different timezone, you are @ -7, and I am @ +8.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
