You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Venkat Ranganathan (JIRA)" <ji...@apache.org> on 2015/03/09 02:03:00 UTC
[jira] [Created] (SQOOP-2191) Provide an option automatically
choose one mapper when neither primary key is defined nor split by column
is provided
Venkat Ranganathan created SQOOP-2191:
-----------------------------------------
Summary: Provide an option automatically choose one mapper when neither primary key is defined nor split by column is provided
Key: SQOOP-2191
URL: https://issues.apache.org/jira/browse/SQOOP-2191
Project: Sqoop
Issue Type: Bug
Reporter: Venkat Ranganathan
Assignee: Venkat Ranganathan
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)