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

Provide an option automatically choose one mapper when neither primary key is defined nor split by column is provided

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.4.4, 1.4.5
    • 1.4.6
    • None
    • None

    Description

      This is typically an issue when import-all-tables is used on a schema. There may be tables without any primary key and currently the only option is identify them and exclude them proactively.

      The solution proposed is to add an option to automatically reset the num mappers to one so that import-all-tables can continue by importing such tables with one mapper

      Attachments

        1. SQOOP-2191-3.patch
          29 kB
          Venkat Ranganathan
        2. SQOOP-2191-2.patch
          28 kB
          Venkat Ranganathan
        3. SQOOP-2191.patch
          12 kB
          Venkat Ranganathan

        Issue Links

          Activity

            People

              venkatnrangan Venkat Ranganathan
              venkatnrangan Venkat Ranganathan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: