Uploaded image for project: 'Sqoop (Retired)'
  1. Sqoop (Retired)
  2. SQOOP-820

Escape table name in export job only if it's required by connector

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 1.4.3
    • None
    • None

    Description

      During investigation on SQOOP-818 I've noticed that automatically escaping table name when saving to mapreduce configuration introduced in SQOOP-601 might cause issues to third party connectors that are expecting that the name won't be ever escaped.

      Attachments

        1. SQOOP-820.patch
          3 kB
          Jarek Jarcec Cecho

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. SQOOP-818 Missing method setConnManager(Lcom/cloudera/sqoop/manager/ConnManager;)V in ExportJobContContext breaks MS SQL Connector

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. SQOOP-540 Microsoft SQL Connector doesn't support custom schemas

          • Major - Major loss of function.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. SQOOP-601 Support custom schemas in PostgreSQL Connector

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Review board

          Activity

            People

              jarcec Jarek Jarcec Cecho
              jarcec Jarek Jarcec Cecho
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment