sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Attila Szabo (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-3066) Introduce an option + env variable to enable/disable SQOOP-2737 feature
Date Sat, 03 Dec 2016 13:41:58 GMT
Attila Szabo created SQOOP-3066:

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

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

View raw message