[
https://issues.apache.org/jira/browse/HBASE-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165606#comment-13165606
]
Lars Hofhansl commented on HBASE-4682:
--------------------------------------
Heh... It takes 46 secs on my machine. Can make it large, too.
As for the messy-ness... The problem is that Delete has strange rules as what
you can do in a single Delete (when you add a deleteFamily all prior
deleteColumn(s) are removed, etc). So deletes have to be written one-by-one to
be correct (that is also why I added the Delete(kv) constructor, rather than an
delete(kv) method).
A put, on the other hand, allows adding all put-related KVs of the same row
into a single Put object. That's why delete-kvs are issued immediately, and
put-kvs are collected into a single Put (that's also what the existing code
does).
It is possible that particular row only has delete markers, so the Put is
created when needed, and only written to the HBase when there were any put-kvs.
> Support deleted rows using Import/Export
> ----------------------------------------
>
> Key: HBASE-4682
> URL: https://issues.apache.org/jira/browse/HBASE-4682
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
> Affects Versions: 0.94.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.0
>
> Attachments: 4682-v1.txt, 4682-v2.txt
>
>
> Parent allows keeping deleted rows around. Would be nice if those could be
> exported and imported as well.
> All the building blocks are there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
