You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Attila Szabo (JIRA)" <ji...@apache.org> on 2016/04/19 23:33:25 UTC

[jira] [Updated] (SQOOP-2910) Add capability to Sqoop to require an explicit option to be specified with --split-by for a String column

     [ https://issues.apache.org/jira/browse/SQOOP-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Attila Szabo updated SQOOP-2910:
--------------------------------
    Attachment: SQOOP-2910.patch

Hi [~jarcec],

I've implemented the solution by using the apache hadoop cofiguration object, so now it's solved with not an argument but with a help of a -D property. I've created test cases for it, however I was not able to test it from CMD line. Could you please ensure that the testing is satisfying!

Thanks in advance!
Attila

> 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
>         Attachments: SQOOP-2910.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)