sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jilani Shaik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3149) Sqoop incremental import - NULL column updates are not pulled into HBase table
Date Tue, 23 May 2017 04:07:05 GMT

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

Jilani Shaik commented on SQOOP-3149:
-------------------------------------

Hi,

Please review this change and let me know if any thing else needed to close this change.

Thanks,
Jilani

> Sqoop incremental import -  NULL column updates are not pulled into HBase table
> -------------------------------------------------------------------------------
>
>                 Key: SQOOP-3149
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3149
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors/generic, hbase-integration
>    Affects Versions: 1.4.6
>            Reporter: Jilani Shaik
>         Attachments: hbase_delete_support_in_incremental_import
>
>
> Sqoop incremental import data from any database to HBase, if source table's column from
a row is updated to NULL, then target HBase table still showing the previous value for that
column. 
> So if you do a scan on the table for that row, HBase shows the previous values of the
column.
> Expected Result: Sqoop incremental import, If NULL columns are there in source, then
HBase need not store that and if it already exists need to delete that column for a given
row.



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

Mime
View raw message