[
https://issues.apache.org/jira/browse/SQOOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051508#comment-15051508
]
Abraham Fine edited comment on SQOOP-2728 at 12/10/15 7:33 PM:
---------------------------------------------------------------
so you can find some documentation about this property here:
https://docs.oracle.com/cd/B28359_01/java.111/b31224/datacc.htm
According to my discussion with [~david.robson], it looks like it would be
possible to get around this is by never calling getObject on a result set
(which is something that we have scattered throughout our code) and instead
calling getTimestamp when we need to. But, I feel that approach may result in
some hard to find bugs down the line.
Is there a way to ensure that mappers run with system properties
programmatically (without overwriting other system properties that may be set
in the cluster's configuration)?
was (Author: abrahamfine):
so you can find some documentation about this property here:
https://docs.oracle.com/cd/B28359_01/java.111/b31224/datacc.htm
According to my discussion with [~david.robson], it looks like it would be
possible to get around this is by never calling getObject on a result set
(which is something that we have scattered throughout our code) and instead
calling getTimestamp when we need to. But, my goal was to keep the GenericJDBC
connector from hav
> Sqoop2: Add documentation regarding the need for
> -Doracle.jdbc.J2EE13Compliant=true when using oracle
> -----------------------------------------------------------------------------------------------------
>
> Key: SQOOP-2728
> URL: https://issues.apache.org/jira/browse/SQOOP-2728
> Project: Sqoop
> Issue Type: Bug
> Reporter: Abraham Fine
> Assignee: Abraham Fine
> Attachments: SQOOP-2728.patch
>
>
> When using the oracle jdbc driver we need to enable
> -Doracle.jdbc.J2EE13Compliant=true so the driver uses java sql standard types
> rather than its own.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
