You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jean Luo (JIRA)" <ji...@apache.org> on 2016/07/21 00:20:20 UTC

[jira] [Commented] (SQOOP-2676) Records are skipped when split-by columns contains NULL values

    [ https://issues.apache.org/jira/browse/SQOOP-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386883#comment-15386883 ] 

Jean Luo commented on SQOOP-2676:
---------------------------------

I encountered a similar issue when using Sqoop to import data from Oracle DB. The split-by column causing the issue was VARCHAR2.

Environment:
Hadoop 2.7.1.2.3.4.29-2
Sqoop 1.4.6.2.3.4.29-1
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production




> Records are skipped when split-by columns contains NULL values
> --------------------------------------------------------------
>
>                 Key: SQOOP-2676
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2676
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.5
>         Environment: Hortonworks: HDP 2.2.4.2
> SQOOP: 1.4.5
> MS SQL: R2008
>            Reporter: Dhaval Modi
>              Labels: import, null, split-by, sqoop
>
> Hi Team,
> This issue occurs when the integral column having NULL value is used in split-by attribute.
> For e.g.
> Col1
> 1
> 2
> NULL
> 3
> 4
> In above example, count of rows is 5, but actually only 4 rows are imported.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)