[
https://issues.apache.org/jira/browse/SQOOP-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhaval Modi updated SQOOP-2664:
-------------------------------
Description:
Hi,
While working with SQOOP, we found an issue where records are duplicated while
importing the data. This is seen when split-by column is of type char(n).
We understand, ideally, integral columns with not null type must be chosen for
split-by column, but in our case, all integral columns has null values. There
is open bug (SQOOP - 2536) raised for this issue.
But as sqoop have support for char datatype to be used in split-by column, and
it giving unexpected results. Thus raising this bug.
was:
Hi,
While work with SQOOP, we found an issue where records are duplicated while
importing data. This is seen when split-by column is of type char(n).
We understand, ideally, integral columns with not null type must be chosen for
split-by column, but in our case, all integral columns has null values. There
is open bug (SQOOP - 2536) raised for this issue.
But as sqoop have support for char datatype to be used in split-by column, and
it giving unexpected results. Thus raising this bug.
> Duplicate records found when split-by column is of type char(n)
> ---------------------------------------------------------------
>
> Key: SQOOP-2664
> URL: https://issues.apache.org/jira/browse/SQOOP-2664
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-jdbc-connector
> Affects Versions: 1.4.5
> Environment: Hortonworks: 2.2.4.2
> Sqoop: 1.4.5
> MS SQL: R2008
> Reporter: Dhaval Modi
>
> Hi,
> While working with SQOOP, we found an issue where records are duplicated
> while importing the data. This is seen when split-by column is of type
> char(n).
> We understand, ideally, integral columns with not null type must be chosen
> for split-by column, but in our case, all integral columns has null values.
> There is open bug (SQOOP - 2536) raised for this issue.
> But as sqoop have support for char datatype to be used in split-by column,
> and it giving unexpected results. Thus raising this bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
