Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-3066

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

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.4.6
    • Fix Version/s: 1.4.7
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              maugli Attila Szabo
              Reporter:
              maugli Attila Szabo

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Issue deployment