You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Selvakumar (JIRA)" <ji...@apache.org> on 2017/04/07 15:22:41 UTC

[jira] [Commented] (SQOOP-3125) NULL updates are not pulled into Hbase whenever incremental load happens in sqoop

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

Selvakumar commented on SQOOP-3125:
-----------------------------------

Do we have a fix available for this issue?

> NULL updates are not pulled into Hbase whenever incremental load happens in sqoop
> ---------------------------------------------------------------------------------
>
>                 Key: SQOOP-3125
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3125
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors/oracle
>    Affects Versions: 1.4.6
>         Environment: MapR Hadoop
>            Reporter: Selvakumar
>
> Ingesting data from Oracle to HBase using Sqoop and fetching data from HBase using Hive tables using HBaseStorageHandler.
> Problem is whenever incremental load happens from Sqoop and if a column is updated with "null",
> HBase doesn't gets updated with null value for that cell and when the data is fetched from HBase using Hive table it fetches last updated timestamp record.
> So the entire record becomes inconsistent as for all the columns it shows updated value and for the "null" column it shows old value of it as timestamp is not updated. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)