sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3066) Introduce an option + env variable to enable/disable SQOOP-2737 feature
Date Mon, 05 Dec 2016 20:01:58 GMT

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

Hudson commented on SQOOP-3066:
-------------------------------

FAILURE: Integrated in Jenkins build Sqoop-hadoop100 #1041 (See [https://builds.apache.org/job/Sqoop-hadoop100/1041/])
SQOOP-3066: Introduce an option + env variable to enable/disable (maugli: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=3e5bab49ea3b48626abe3b6316820159fe4bed41])
* (edit) src/java/org/apache/sqoop/manager/oracle/OraOopOracleQueries.java
* (edit) src/java/org/apache/sqoop/manager/oracle/OraOopConnManager.java
* (edit) src/java/org/apache/sqoop/mapreduce/db/OracleDBRecordReader.java
* (edit) src/java/org/apache/sqoop/manager/oracle/OraOopOutputFormatUpdate.java
* (edit) src/java/org/apache/sqoop/manager/oracle/OraOopDBRecordReader.java
* (edit) src/java/org/apache/sqoop/manager/OracleManager.java
* (edit) src/java/org/apache/sqoop/manager/oracle/OraOopOutputFormatInsert.java
* (edit) src/java/org/apache/sqoop/manager/oracle/OracleUtils.java
* (edit) src/java/org/apache/sqoop/SqoopOptions.java
* (edit) src/java/org/apache/sqoop/tool/BaseSqoopTool.java
* (edit) src/test/com/cloudera/sqoop/TestSqoopOptions.java
* (edit) src/test/org/apache/sqoop/manager/oracle/util/OracleData.java
* (edit) src/java/org/apache/sqoop/manager/oracle/OraOopOutputFormatBase.java


> Introduce an option + env variable to enable/disable SQOOP-2737 feature
> -----------------------------------------------------------------------
>
>                 Key: SQOOP-3066
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3066
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.6
>            Reporter: Attila Szabo
>            Assignee: Attila Szabo
>            Priority: Critical
>             Fix For: 1.4.7
>
>         Attachments: SQOOP-3066.patch
>
>
> After [SQOOP-2737] several users ran into that their SQOOP commands are failing due to
the fact the original commands were not phrased cases sensitive table/column/schema names
in mind.
> There had been also another outcome of this feature, that the "--split-by" option does
not accept Oracle functions anymore (e.g. MOD(col_name,4) ), as after correct escaping+quoting
it would be handled by Oracle as a db col name, instead of an expression to evaluate.
> My goal here is to introduce an option to turn on/off the (fully proper and industry
standard) escaping implemented in [SQOOP-2737], and also add an environment variable support
for that, thus users would have the backward compatible fallback plan, and not changing their
command.
> I do also plan to implement an argument for supporting split-by with database functions/expressions,
and thus the escaping and the split-by expressions features would become independent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message