[SQOOP-3267] Incremental import to HBase deletes only last version of column

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.7
• Fix Version/s: 1.5.0
• Component/s: hbase-integration
• Assignee: Daniel Voros
• Reporter: Daniel Voros
• Created: 01/Dec/17 17:34
• Updated: 22/Feb/18 14:38
• Resolved: 22/Feb/18 14:21

Description

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?

Issue Links

• is required by: SQOOP-3276 Enable import of null columns to HBase
• links to: Review