[
https://issues.apache.org/jira/browse/SQOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237190#comment-14237190
]
Jarek Jarcec Cecho commented on SQOOP-1845:
-------------------------------------------
I think that we should clearly define the object model via SQOOP-1829.
Depending on third party library seems indeed slightly troublesome especially
given the fact that Hadoop is particularly bad with classpath isolation and can
impose on us different versions that we would like to use. Another idea would
be to create our own "wrapper" classes for certain types, so that we can swap
the libraries (implementation) in the future.
> 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)
