You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Attila Szabo (JIRA)" <ji...@apache.org> on 2016/12/06 15:57:58 UTC

[jira] [Created] (SQOOP-3071) Fix OracleManager to apply localTimeZone correctly in case of Date objects too

Attila Szabo created SQOOP-3071:
-----------------------------------

             Summary: 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


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)