Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates
 209.85.161.169 as permitted sender)
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <1333433253.51443.YahooMailNeo@web121704.mail.ne1.yahoo.com>
References: 
 <CAGpTDNe3nf9YMBe7qFuL5CjgYmchFBH64v2YSxvR7YzdqwUwzA@mail.gmail.com>
	<1333415097.50247.YahooMailNeo@web121702.mail.ne1.yahoo.com>
	<CADcMMgHb_8C_kFLfd49PH5SMpakfKSMJ58NZq5vQ-rzyGv-mGg@mail.gmail.com>
	<1333433253.51443.YahooMailNeo@web121704.mail.ne1.yahoo.com>
Date: Tue, 3 Apr 2012 09:43:27 -0700
Message-ID: 
 <CAGpTDNd4KXsiXvPJJTji=X6PThS3m6FdDSvQL5uYrjif07WdEQ@mail.gmail.com>
Subject: Re: Pull instant schema updating out?
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: dev@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I found this problem after looking at it for 5 minutes and it features
bugs without even being enabled. I'm wondering if that tree is hiding
a massive forrest or not.

J-D

On Mon, Apr 2, 2012 at 11:07 PM, lars hofhansl <lhofhansl@yahoo.com> wrote:
> I did a superficial review of HBASE-4213 and remember I was quite exited =
about the promise of the change at
> that time. If the problem is just with the MonitoredTask behavior (as ind=
icated in HBASE-5702) I'd say we try to fix that.
>
> -- Lars
>
>
>
> ________________________________
> =A0From: Stack <stack@duboce.net>
> To: dev@hbase.apache.org; lars hofhansl <lhofhansl@yahoo.com>
> Sent: Monday, April 2, 2012 9:05 PM
> Subject: Re: Pull instant schema updating out?
>
> On Mon, Apr 2, 2012 at 6:04 PM, lars hofhansl <lhofhansl@yahoo.com> wrote=
:
>> How much duplicate code are we talking about? Do these share common code=
 to close/open the regions, or is it a completely different code path? (I k=
now I could look myself, but it's easier to ask)
>>
>> From a gut reaction it feels cleaner to keep track of the state of the a=
lter in ZK.
>>
>>
>
> Both are incomplete.=A0 The approaches share no code.=A0 The conversation
> Ted cites is from nearly a year ago (and is nought but our platitudes
> that the authors get together on the problem which didn't happen; the
> context did not help w/ one part-time on the job and the other a
> summer intern).=A0 Neither has a sponsor.=A0 The "Online schema update" i=
s
> at least used in a few places, cautiously.=A0 What should happen is we
> should pull out both and replace with a working online schema
> mechanism.=A0 Until that happens undo at least one of them before
> someone other than J-D gets hurt.=A0 I vote for pulling=A0 "Online schema
> update".
>
> St.Ack