[
https://issues.apache.org/jira/browse/HBASE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148728#comment-13148728
]
Lars Hofhansl commented on HBASE-4721:
--------------------------------------
I think the point Prakash was making is that we only have keep the deletes in
the store files (the delete markers), but not the deleted KVs (the puts that
would be affected by the deletes), since the replication would be using the
logs anyway.
In your scenario above... As long as we keep the deletes at the target for a
while, it won't be a problem if the puts arrive later (both will retain the
time stamp from the source).
That is what Prakash wants to achieve with this.
> Retain Delete Markers after Major Compaction
> --------------------------------------------
>
> Key: HBASE-4721
> URL: https://issues.apache.org/jira/browse/HBASE-4721
> Project: HBase
> Issue Type: New Feature
> Reporter: Prakash Khemani
> Assignee: Prakash Khemani
>
> There is a need to provide long TTLs for delete markers. This is useful when
> replicating hbase logs from one cluster to another. The receiving cluster
> shouldn't compact away the delete markers because the affected key-values
> might still be on the way.
--
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
