[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257930#comment-16257930
]
stack commented on HBASE-17852:
-------------------------------
bq. Stack, are you essentially asking why this isn't implemented on top of
ProcV2?
bq. I think at this point, it would be more productive if we can say more
"there is something implicitly broken with this approach" instead of "there is
a more elegant implementation to be had".
I am not asking for any particular implementation, to be clear. I'm just trying
to understand and am having trouble digesting full restore of a meta table
whatever the size or traffic on error. It strikes me as whack (You seem to at
least agree it 'overkill'). There seems to be no write-up on the approach here
ahead of piecemeal code drops (w/o overarching description of what all is
entailed) so only way to figure it as best as I can ascertain, is via this
really pleasant back and forth w the author.
Vlad, you seem to be doing your utmost to sabotage the delivery of this
feature. The sort of answers you give us reviewers is one thing. Will operators
who run into issues w/ this feature get the same treatment?
> Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental
> backup)
> ------------------------------------------------------------------------------------
>
> Key: HBASE-17852
> URL: https://issues.apache.org/jira/browse/HBASE-17852
> Project: HBase
> Issue Type: Sub-task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-17852-v1.patch, HBASE-17852-v2.patch,
> HBASE-17852-v3.patch, HBASE-17852-v4.patch, HBASE-17852-v5.patch,
> HBASE-17852-v6.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
