[SQOOP-2191] Provide an option automatically choose one mapper when neither primary key is defined nor split by column is provided

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.4, 1.4.5
• Fix Version/s: 1.4.6
• Assignee: Venkat Ranganathan
• Reporter: Venkat Ranganathan
• Created: 09/Mar/15 00:59
• Updated: 14/Mar/15 01:07
• Resolved: 13/Mar/15 23:59

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

Issue Links

• links to: review board link