[
https://issues.apache.org/jira/browse/SQOOP-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248919#comment-15248919
]
Hudson commented on SQOOP-2910:
-------------------------------
FAILURE: Integrated in Sqoop-hadoop20 #1047 (See
[https://builds.apache.org/job/Sqoop-hadoop20/1047/])
SQOOP-2910: Add capability to Sqoop to require an explicit option to be
(jarcec:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=660f3e8ad07758aabf0a9b6ede3accdfac5fb1be])
* src/java/org/apache/sqoop/mapreduce/db/TextSplitter.java
*
src/test/org/apache/sqoop/mapreduce/db/TextSplitterHadoopConfIntegrationTest.java
> Add capability to Sqoop to require an explicit option to be specified with
> --split-by for a String column
> ---------------------------------------------------------------------------------------------------------
>
> Key: SQOOP-2910
> URL: https://issues.apache.org/jira/browse/SQOOP-2910
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Attila Szabo
> Assignee: Attila Szabo
> Fix For: 1.4.7
>
> Attachments: SQOOP-2910.patch, SQOOP-2910_1.patch
>
>
> In the past several users faced issues when they tried to import String
> columns with the --split-by option. They didn't except to have any kind of
> issues/side effects, however this is a well known issue in Sqoop (and AFAIK
> we don't plan to change this behaviour).
> The objective here is to require the customer to explicitly choose to split
> by string which is known to have issues.
> {code}
> --split-by <CHAR_COLUMN> --i-know-what-i-am-doing
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
