Sqoop
  1. Sqoop
  2. SQOOP-529

Enforce usage of --driver and --connection-manager parameters

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.2
    • Component/s: None
    • Labels:
      None

      Description

      Choosing and creating connection manager instance is very tricky in current Sqoop code. Sqoop will defer the choice to loaded factory classes - only DefaultManagerFactory is used by default. This default class implements logic for --driver and --connection-manager parameters. However user also do have option to add own factories that do not necessarily have the same behavior.

      This is very tricky as it actually depends on user environment (which factories are loaded) whether --driver and --connection-manager properties will work as expected (~ the same way all the time).

      I would like to suggest putting logic around --driver and --connection-manager out of DefaultManagerFactory to enforce their usage in all cases.

      1. SQOOP-529.patch
        6 kB
        Jarek Jarcec Cecho
      2. SQOOP-529.patch
        6 kB
        Jarek Jarcec Cecho
      3. SQOOP-529.patch
        6 kB
        Jarek Jarcec Cecho

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Jarek Jarcec Cecho
              Reporter:
              Jarek Jarcec Cecho
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development