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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.7
• Assignee: Attila Szabo
• Reporter: Attila Szabo
• Created: 06/Dec/16 15:57
• Updated: 16/Jun/17 04:29
• Resolved: 06/Dec/16 16:56

Description

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.

Issue Links

• links to: Review board