[
https://issues.apache.org/jira/browse/SQOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236525#comment-14236525
]
Veena Basavaraj commented on SQOOP-1845:
----------------------------------------
[~jarcec] [[~abec]I started to fix this and realized another thing with JODA
Joda's DateTime class does not allow finer precision than milliseconds, as you
can see in the API docs. So, unfortunately, you won't be able to store
microseconds in a DateTime.
and our specs want to have 6 digit [.zzzzz]
http://www.joda.org/joda-time/apidocs/org/joda/time/DateTime.html
> 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: Qian Xu
> Attachments: 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)
