hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <sean.bus...@gmail.com>
Subject Re: Moving 2.0 forward
Date Mon, 31 Jul 2017 14:10:57 GMT
+1 on a dedicated thread for upgrade expectations.

On Mon, Jul 31, 2017 at 8:04 AM, Stack <stack@duboce.net> wrote:
> On Wed, Jul 26, 2017 at 10:57 PM, ashish singhi <ashish.singhi@huawei.com>
> wrote:
>
>> One question regarding upgrade:
>> Do we expect the user to move to latest branch-1 release and then upgrade
>> to 2.0 version ?
>>
>>
> I think, as you seem to, that this is too much to ask Ashish.
>
> I think we should support at the low end going from 1.0.0 to 2.0.0; i.e.
> you'd have to upgrade to 1.x if you were running 0.98 before you could go
> to 2.0.0.
>
> What do folks think of this? I should start a separate thread on upgrade
> expectations?
>
> St.Ack
>
>
>
>> I think that should not be imposed on the user.
>>
>> Regards,
>> Ashish
>>
>> -----Original Message-----
>> From: 张铎(Duo Zhang) [mailto:palomino219@gmail.com]
>> Sent: 26 July 2017 12:10
>> To: dev@hbase.apache.org
>> Subject: Re: Moving 2.0 forward
>>
>> I set HBASE-18169 as a Blocker because I found some critial problems on
>> our current CPs. The semantics are broken. Although we are allowed to break
>> CP in a major release, I think we need to provide the same ability(in
>> another way).
>>
>> 2017-07-25 1:25 GMT+08:00 Josh Elser <elserj@apache.org>:
>>
>> >
>> >
>> > On 7/21/17 12:03 PM, Stack wrote:
>> >
>> >> Status update girls and boys!
>> >>
>> >> hbase-2.0.0-alpha1 went out June 22nd.
>> >>
>> >> alpha2 has been a bit slow to follow (holidays) though there has been
>> >> steady progress closing out blockers and criticals by a bunch of you
>> all.
>> >> The plan is for a release in the first week or so of August. It
>> >> should be fully up on hbase-thirdparty using updated (and relocated)
>> >> versions of netty, guava, and protobuf as well as a default deploy
>> >> that has master-carrying-no-regions.
>> >>
>> >> alpha3 will follow soon after and will focus on making sure our
>> >> user-facing APIs are clean (branch-1 compatible, no illicit
>> >> removals/mods, and so on) and that basic upgrade 'works'.
>> >>
>> >> betas start in September?
>> >>
>> >> I've been keeping a rough general state here [1] (please update any
>> >> section that is lagging actuality) but for details on what blockers
>> >> and criticals remain, see the JIRA 2.0 view [2]. Recent
>> >> issue-gardening has brought 2.0 into better focus. Feel free to
>> >> review and punt items you think can wait till 3.0 or 2.1. If you want
>> >> to pull in more stuff, please ask first.
>> >>
>> >
>> > Chia-Ping (I think? -- JIRA is being a pain) had asked on the
>> > space-quota
>> > phase2 work (include size of hbase snapshots in a table's "quota
>> > usage") if we should try to also include that work in 2.0.
>> >
>> > I like the idea of this also hitting 2.0 as it would make the feature
>> > a bit more "real", but am obviously a little nervous (I have no reason
>> > to be nervous though). I am pretty happy with the feature in terms of
>> > how much it is covered via testing.
>> >
>> > https://issues.apache.org/jira/browse/HBASE-17748
>> >
>> >
>> > Thanks,
>> >> St.Ack
>> >>
>> >> 1.
>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> >> Eu_ktczrlKHK8N4SZzs/edit#
>> >> 2. https://issues.apache.org/jira/projects/HBASE/versions/12327188
>> >>
>> >
>> > - Josh
>> >
>>



-- 
Sean

Mime
View raw message