assignee for (HBASE-4071) Data GC: Remove all versions > TTL EXCEPT the last written version

[Ted Yu <yu...@gmail.com>]

Lars:
Since 4071 doesn't currently have an assignee, you can certainly assign to
yourself.

You can optionally send an email to dev@ informing other HBase developers of
your intention to complete HBASE-4071

Keep up the good work.

On Fri, Aug 19, 2011 at 10:26 AM, Lars Hofhansl (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/HBASE-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087813#comment-13087813]
>
> Lars Hofhansl commented on HBASE-4071:
> --------------------------------------
>
> Any objections if I assigned this jira to me?
>
> > Data GC: Remove all versions > TTL EXCEPT the last written version
> > ------------------------------------------------------------------
> >
> >                 Key: HBASE-4071
> >                 URL: https://issues.apache.org/jira/browse/HBASE-4071
> >             Project: HBase
> >          Issue Type: New Feature
> >            Reporter: stack
> >         Attachments: MinVersions.diff
> >
> >
> > 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.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>