[
https://issues.apache.org/jira/browse/SQOOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726160#comment-15726160
]
Hudson commented on SQOOP-3071:
-------------------------------
FAILURE: Integrated in Jenkins build Sqoop-hadoop23 #1280 (See
[https://builds.apache.org/job/Sqoop-hadoop23/1280/])
SQOOP-3071: Fix OracleManager to apply localTimeZone correctly in case (maugli:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=fe67a0a5c0a6875e3cd3e87feb3df1a73939be57])
* (edit) src/java/org/apache/sqoop/manager/OracleManager.java
> Fix OracleManager to apply localTimeZone correctly in case of Date objects too
> ------------------------------------------------------------------------------
>
> Key: SQOOP-3071
> URL: https://issues.apache.org/jira/browse/SQOOP-3071
> Project: Sqoop
> Issue Type: Bug
> Reporter: Attila Szabo
> Assignee: Attila Szabo
> Attachments: SQOOP-3071.patch
>
>
> In the current implementation OraOop and OracleManager are different from the
> POV of setting sessionTimeZone in oracle.
> OracleManager does not set the TimeZone in java, and neither the default
> timeZone on the Oracle connection.
> Thus when the local timezone realted data is retrieved by Sqoop as not a
> String object, but as a Date, the timeZone information is lost, and this
> could cause confusion/bogus behaviour on user side.
> The goal is to get inline the two implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
