[SQOOP-3066] Introduce an option + env variable to enable/disable SQOOP-2737 feature

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4.6
• Fix Version/s: 1.4.7
• Assignee: Attila Szabo
• Reporter: Attila Szabo
• Due: 07/Dec/16
• Created: 03/Dec/16 13:41
• Updated: 29/Aug/17 13:58
• Resolved: 16/Jun/17 04:56

Description

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.

Issue Links

• is depended upon by: SQOOP-3067 Add an cmd line option to support split-by feature for database functions/expressions
• links to: Review ticket