Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
-
Even if older than TTL, keep N versions; e.g. if N is 1, we'll purge all versions but the most recent written even if this one version is older than TTL.
Description
We were chatting today about our backup cluster. What we want is to be able to restore the dataset from any point of time but only within a limited timeframe – say one week. Thereafter, if the versions are older than one week, rather than as we do with TTL where we let go of all versions older than TTL, instead, let go of all versions EXCEPT the last one written. So, its like versions==1 when TTL > one week. We want to allow that if an error is caught within a week of its happening – user mistakenly removes a critical table – then we'll be able to restore up the the moment just before catastrophe hit otherwise, we keep one version only.
Attachments
Attachments
Issue Links
- is related to
-
HBASE-3842 Refactor Coprocessor Compaction API
- Closed
- relates to
-
HBASE-2600 Change how we do meta tables; from tablename+STARTROW+randomid to instead, tablename+ENDROW+randomid
- Closed