[
https://issues.apache.org/jira/browse/HBASE-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456491#comment-13456491
]
Lars Hofhansl commented on HBASE-6796:
--------------------------------------
@Stack: We will have needed it at Salesforce if an admin type person
accidentally dropped a table... Unless that happens we will not have needed it.
:)
Seriously though, I think for a database these data retention policies are
essential. So the question is: Is the added data safety outweighed by the risk
introduced by new code?
Maybe Salesforce is special here. Our capital is that we never lose data.
Period.
If our needs do not align with the community here, we could obviously maintain
this as private patch on top of 0.94. But for obvious reasons I am trying to
avoid that.
@Stack: What's your thinking about an 0.96 timeline? When do you think it would
be stable?
(I know I am asking for a shot in the dark here. There are 173 open issues
against it still, so it's hard to say?)
@Ted, I absolutely agree with you, that we need to track down the test failures
in trunk before this can considered for backporting.
@Jesse, can you have a look at HBASE-6439, HBASE-6797, and HBASE-6707?
> Backport HBASE-5547, Don't delete HFiles in backup mode.
> --------------------------------------------------------
>
> Key: HBASE-6796
> URL: https://issues.apache.org/jira/browse/HBASE-6796
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Jesse Yates
> Fix For: 0.94.3
>
> Attachments: hbase-5547-0.94-backport-v0.patch
>
>
> See HBASE-5547
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
