You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Daniel Voros (JIRA)" <ji...@apache.org> on 2017/12/01 17:35:00 UTC
[jira] [Created] (SQOOP-3267) Incremental import to HBase deletes
only last version of column
Daniel Voros created SQOOP-3267:
-----------------------------------
Summary: Incremental import to HBase deletes only last version of column
Key: SQOOP-3267
URL: https://issues.apache.org/jira/browse/SQOOP-3267
Project: Sqoop
Issue Type: Bug
Components: hbase-integration
Affects Versions: 1.4.7
Reporter: Daniel Voros
Deletes are supported since SQOOP-3149, but we're only deleting the last version of a column when the corresponding cell was set to NULL in the source table.
This can lead to unexpected and misleading results if the row has been transferred multiple times, which can easily happen if it's being modified on the source side.
Also SQOOP-3149 is using a new Put command for every column instead of a single Put per row as before. This could probably lead to a performance drop for wide tables (for which HBase is otherwise usually recommended).
[~jilani], [~anna.szonyi] could you please comment on what you think would be the expected behavior here?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)