[
https://issues.apache.org/jira/browse/SQOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235205#comment-14235205
]
Veena Basavaraj edited comment on SQOOP-1845 at 12/5/14 7:34 AM:
-----------------------------------------------------------------
thanks Qian, https://issues.apache.org/jira/browse/SQOOP-1846 only addressed
the input format we expect, but I am still not clear we have a good story for
the use case where the timezone is missing in the input for dateTime.
i.e "'2014-10-01T12:00:00.000', how should this appear after is parsed using
DateTime.parse in JODA.
your proposal for this is to detect the local timezone ?
Should timezone be even optional in the date time use case? is my question
was (Author: vybs):
thanks Qian, https://issues.apache.org/jira/browse/SQOOP-1846 only addressed
the input format we expect, but I am still not clear we have a good story for
the use case where the timezone is missing in the input for date tme.
your proposal for this is to detect the local timezone ?
Should timezone be even optional in the date time use case? is my question
> 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)
