Attila Szabo created SQOOP-3085:
-----------------------------------
Summary: Add support for client side (JVM) timezone settings
Key: SQOOP-3085
URL: https://issues.apache.org/jira/browse/SQOOP-3085
Project: Sqoop
Issue Type: Improvement
Affects Versions: 1.4.6
Reporter: Attila Szabo
Assignee: Attila Szabo
Fix For: 1.4.7
Currently in OracleManager and OraOopManager there is the capability to set
time zone to support "TIMESTAMP WITH LOCAL TIME ZONE" data types (with
"oracle.sessionTimezone" Hadoop option).
As the current user expectation (+3rd party test case) is to get back the date
in the given local time zone, both OracleManager and OraOopManager sets the
default time zone of the underlying JVM to the same time zone, what is passed
to the Oracle connection.
This is a very straightforward and consistent expectation, however there's a
need to set the time zone settings in Sqoop through command line arguments.
There are two arguments for that:
A - passing the -Duser.timezone to the JVM is not always that straightforward
(as sqoop is executed by some shell/batch script, and user would have to modify
that file, or modify the hadoop/sqoop site xml files, or pass it with env)
B - if the user wants to set the client side time zone, it should be explicit
on the CMD line, and also warning+validation should be returned if the client
side+db side time zones are different (by intention).
The goal of this task is to fill in this gap, and add the option+the required
validation too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
