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

Add support for requiring that a connector be used, otherwise the job should fail

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Invalid
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.4.3
    • Component/s: connectors
    • Labels:
      None

      Description

      There are situations where it is critical that a specific connector be used during a Sqoop. For example, if you have a table that doesn't have a suitable column for partitioning, and thus you're relying on OraOop's row-based partitioning, then it's critical that OraOop be used. If the Sqoop request falls back to the generic Oracle connector, this puts huge, unacceptable load on the database.

      The proposal is to add a -connector <class name> parameter, which will cause the job to fail unless it's handled by the connector (from sqoop.ConnFactory.getManager) with the matching class name.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kkrugler Ken Krugler
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: