[ https://issues.apache.org/jira/browse/HBASE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prakash Khemani updated HBASE-4721: ----------------------------------- Summary: Retain Delete Markers after Major Compaction (was: Configurable TTL for Delete Markers) I think all we need to do is to retain delete markers even after a major compaction. Retaining delete markers beyond the ttl of regular KVs doesn't make sense to me. Say the regular KV TTL is 1 day. If we keep a delete marker alive for 2 days then the only KVs that it is going to affect are the ones that are older than 2 days and are already expired. If we just retain delete markers after every major compaction then the processing becomes exactly the same as in a minor compaction. Hopefully, will reduce some code complexity. > 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