We at Huawei have been testing this for more than 8 months now, did not find any critical issues thus far and launched a service on Huawei public cloud also which is based HBase 1.3.1 version. With that, I am +1 on moving the stable pointer.
Regards, Ashish -----Original Message----- From: Zach York [mailto:zyork.contribut...@gmail.com] Sent: Tuesday, February 06, 2018 3:28 AM To: dev@hbase.apache.org Subject: Re: Considering branching for 1.5 and other branch-1 release planning > If someone else is using 1.3 your feedback would be very valuable. EMR has shipped the 1.3 line since EMR 5.4.0 (March 08, 2017). We have not ran into any unresolved critical issues and it has been fairly stable overall. I would be a +1 on moving the stable pointer. Thanks, Zach On Mon, Feb 5, 2018 at 1:30 PM, Andrew Purtell <andrew.purt...@gmail.com> wrote: > Thanks so much for the feedback Francis. > > I think we are just about there to move the stable pointer. > > > On Feb 5, 2018, at 9:48 AM, Francis Liu <tof...@apache.org> wrote: > > >> If someone else is using 1.3 your feedback would be very > > valuable. > > > > We are running 1.3 in production, full rollout ongoing. Ran into > > some issues but it's generally been stable. We'll prolly gonna be on > > 1.3 for a while. > > > > Cheers, > > Francis > > > > > >> On Sun, Feb 4, 2018 at 10:59 AM Andrew Purtell > >> <apurt...@apache.org> > wrote: > >> > >> Hi Ted, > >> > >> If Hadoop 3 support is in place for an (eventual) 1.5.0 release, I > >> think that would be great. > >> > >> > >>> On Sun, Feb 4, 2018 at 10:55 AM, Ted Yu <yuzhih...@gmail.com> wrote: > >>> > >>> Andrew: > >>> Do you think making 1.5 release support hadoop 3 is among the goals ? > >>> > >>> Cheers > >>> > >>> On Fri, Feb 2, 2018 at 3:28 PM, Andrew Purtell > >>> <apurt...@apache.org> > >>> wrote: > >>> > >>>> The backport of RSGroups to branch-1 triggered the opening of the > >>>> 1.4 > >>> code > >>>> line as branch-1.4 and releases 1.4.0 and 1.4.1. > >>>> > >>>> After the commit of HBASE-19858 (Backport HBASE-14061 (Support > CF-level > >>>> Storage Policy) to branch-1), storage policy aware file placement > might > >>> be > >>>> useful enough to trigger a new minor release from branch-1. This > >>>> would > >> be > >>>> branch-1.5, and at least release 1.5.0. I am not sure about this yet. > >> It > >>>> needs testing. I'd like to mock up a couple of use cases and > >>>> determine > >> if > >>>> what we have is sufficient on its own or more changes will be needed. > I > >>>> want to get the idea of a 1.5 on your radar. though. > >>>> > >>>> Also, I would like to make one more release of branch-1.3 before > >>>> we > >>> retire > >>>> it. Mikhail passed the reins. We might have a volunteer to RM 1.3.2. > If > >>>> not, I will do it. I'm expecting 1.4 will supersede 1.3 but this > >>>> will > >> be > >>>> decided organically depending on uptake. > >>>> > >>>> -- > >>>> Best regards, > >>>> Andrew > >>>> > >>>> Words like orphans lost among the crosstalk, meaning torn from > >>>> truth's decrepit hands > >>>> - A23, Crosstalk > >>>> > >>> > >> > >> > >> > >> -- > >> Best regards, > >> Andrew > >> > >> Words like orphans lost among the crosstalk, meaning torn from > >> truth's decrepit hands > >> - A23, Crosstalk > >> >
