[ https://issues.apache.org/jira/browse/SQOOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726043#comment-15726043 ] 

ASF subversion and git services commented on SQOOP-3071:
--------------------------------------------------------

Commit fe67a0a5c0a6875e3cd3e87feb3df1a73939be57 in sqoop's branch refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=fe67a0a ]

SQOOP-3071: Fix OracleManager to apply localTimeZone correctly in case of Date objects too

(Attila Szabo)


> 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)