[
https://issues.apache.org/jira/browse/SQOOP-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jilani Shaik updated SQOOP-3149:
--------------------------------
Description:
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.
was:
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 should provide a support to delete
those columns which are NULL in source, As HBase will not store the NULL
columns.
> 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
>
> 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)
