On Wed, Nov 1, 2017 at 11:33 AM, Vladimir Rodionov <[email protected]> wrote:
> >> hbase-backup: Not done and it doesn't look like it will be done for > beta-1. > >>It can come in later in a 2.1 or 3.0 when it is finished. > > That is not correct. All blockers have been resolved, the last one has a > patch which is ready to be commited. > > Salesforce team has conducted independent testing and found no issues with > a functionality to my best knowledge. > > Explain please, Stack. > > I've not done in-depth research so could be wrong about backup, but from my perch, I've seen the recent filings against backup, HBASE-19104-19109, which strike me as pretty basic missing facility. The new issues go without comment (caveat a single question). I've seen no evidence of extensive test (scale?). The last issue I looked at has backup putting up two system tables with presumptions about assignment order we do not (as yet) support. I've always had trouble eliciting state of the feature; summary of capability and what is to do are hard to come by. I'm trying to avoid rolling out features before they are baked. We've made this mistake a good few times in the past (e.g. DLR). Thanks, St.Ack > > > On Wed, Nov 1, 2017 at 10:32 AM, Stack <[email protected]> wrote: > > > I want to purge the below list of modules, features, and abandoned code > > from branch-2 before we make a beta-1 (4-5 weeks I'm thinking). Lets > > discuss. Some are already scheduled for removal but listing anyways for > > completeness sake. Pushback or other suggestions on what else we should > > remove are welcome. > > > > Distributed Log Replay: Just last week, I heard of someone scheduling > > testing of DLR. We need to better message that this never worked and > was/is > > not supported. It's a good idea that we should implement but built on a > > different chasis (procedurev2?). Meantime, DLR is still scattered about > the > > codebase as an optional code path. Lets remove it. > > > > hbase-native-client: It is not done and won't be for 2.0.0. It can come > in > > later when it is done (2.1 or 3.0). > > > > hbase-prefix-tree: A visionary effort that unfortunately has had no > uptake > > since its original wizard-author moved on. I don't believe it is used > > anywhere. It has become a drag as global changes need to be applied in > here > > too by folks who are not up on how it works probably doing damage along > the > > way. This is like DLR in it should be first class but we've not done the > > work to keep it up. > > > > hbase-backup: Not done and it doesn't look like it will be done for > beta-1. > > It can come in later in a 2.1 or 3.0 when it is finished. > > > > hbase-spark: Purging this makes me tear-up. > > > > What else? > > > > Thanks, > > St.Ack > > >
