[
https://issues.apache.org/jira/browse/SQOOP-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535656#comment-13535656
]
Hudson commented on SQOOP-652:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop20 #395 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop20/395/])
SQOOP-652: Improve error message generated in DataDrivenDBInputFormat when
no splitter is available (Revision 0e8a7dc73e4b8fa64a8c222384fe0027045b8a17)
Result = SUCCESS
jarcec :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=0e8a7dc73e4b8fa64a8c222384fe0027045b8a17
Files :
* src/java/org/apache/sqoop/mapreduce/db/DataDrivenDBInputFormat.java
> Improve error message generated in DataDrivenDBInputFormat when no splitter
> is available
> -----------------------------------------------------------------------------------------
>
> Key: SQOOP-652
> URL: https://issues.apache.org/jira/browse/SQOOP-652
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.2
> Reporter: Jarek Jarcec Cecho
> Assignee: Linden Hillenbrand
> Priority: Trivial
> Labels: newbie
> Fix For: 1.4.3
>
> Attachments: DataDrivenDBInputFormat.patch
>
>
> Currently DataDrivenDBInputFormat will throw following exception in case that
> there is no available Splitter:
> {code}
> DBSplitter splitter = getSplitter(sqlDataType);
> if (null == splitter) {
> throw new IOException("Unknown SQL data type: " + sqlDataType);
> }
> {code}
> Text of the exception is very confusing as it's not describing what has
> actually happened. Would be great if this message would be improved by saying
> that Sqoop do not have splitter for given sql type and therefore user should
> either use different split column (argument --split-by) or lower number of
> mappers to 1 (splitters are not used in such case).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
