Has any change been done in the past half year on "Online schema update" ?
When we make such an important decision, we should evaluate various factors. "Instant schema alter" has better design: it endures master failover. If the following tests can be written for "Online schema update" and pass, I would vote for it: src/test/java/org/apache/hadoop/hbase/client/TestInstantSchemaChange.java src/test/java/org/apache/hadoop/hbase/client/TestInstantSchemaChangeFailover.java src/test/java/org/apache/hadoop/hbase/client/TestInstantSchemaChangeSplit.java Otherwise I am -1 on pulling "Instant schema alter" There is more work to be done: reduce the noise posed by MonitoredTask, throttling, etc. But these are not difficult tasks. On Tue, Apr 3, 2012 at 9:14 AM, lars hofhansl <[email protected]> wrote: > If we pull it out it'll never get fixed. :) > > I don't really have strong feelings about this, just that functional > schema changes without disabling the table are a pretty important feature. > If it's not working and there's no reasonable chance to get it fixed, > because nobody is working on it, then let's pull it. > > > > ________________________________ > From: Stack <[email protected]> > To: [email protected]; lars hofhansl <[email protected]> > Sent: Tuesday, April 3, 2012 7:50 AM > Subject: Re: Pull instant schema updating out? > > On Mon, Apr 2, 2012 at 11:07 PM, lars hofhansl <[email protected]> > wrote: > > If the problem is just with the MonitoredTask behavior (as indicated in > HBASE-5702) I'd say we try to fix that. > > > > Who is the 'we' in the above? Its not been touched since committed. > Other issues are it does an explosive close-all and then open-all on a > table; there should be dampening. How about pulling it out till its > fixed. > St.Ack >
