[
https://issues.apache.org/jira/browse/SQOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235693#comment-14235693
]
Veena Basavaraj commented on SQOOP-1845:
----------------------------------------
thats just the spec and theory, I would like [~jarcec] to address how the
implementation will be
But when it gets to an implementation detail, are we going to parse the String
to see if it has timezone or not and make this call? I would have rather made
this mandatory to avoid these intermediate parsing logic to infer if timezone
is there or not.
Secondly, the JODA library we use expects a DateTime.parse(dateTimeString,
timeZone) , and we have to provide a timeZone.
> Unit test failed due to different timezone
> ------------------------------------------
>
> Key: SQOOP-1845
> URL: https://issues.apache.org/jira/browse/SQOOP-1845
> Project: Sqoop
> Issue Type: Bug
> 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)
