[
https://issues.apache.org/jira/browse/SQOOP-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361351#comment-14361351
]
ASF subversion and git services commented on SQOOP-2191:
--------------------------------------------------------
Commit 2576ca2f03a7929f7ff1d4b10867fdee382e8856 in sqoop's branch
refs/heads/trunk from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=2576ca2 ]
SQOOP-2191: Provide an option automatically choose one mapper when neither
primary key is defined nor split by column is provided
(Venkat Ranganathan via Jarek Jarcec Cecho)
> 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
> Affects Versions: 1.4.4, 1.4.5
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Fix For: 1.4.6
>
> Attachments: SQOOP-2191-2.patch, SQOOP-2191.patch
>
>
> 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)
