2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai <chia7...@apache.org>:

> > As I volunteered to be the release manager for the 2.1 release line so
> let
> > me bring this up.
> +1 to Duo be RM of 2.1 release.
>
> > disabled from 2.0.0 release, for example, serial replication, and in
> memory compaction
> IIRC, in memory compaction is enabled in 2.0 and the default policy is
> BASIC. (please correct me if I misunderstand something.)
>
We disabled it by default in the end due to some performance issues...

>
> > For the 2.1 release line, I would like to define it as the 'real' 2.x
> Seems the release date between 2.0 and 2.1 will be very close. Is it
> related to our new release plan? (IIRC, Andrew had suggested some great
> release plan based time. But I fail to find the thread...)
>
> > And for the 3.0.0 release, I think the new features should be decided
> ASAP.
> > We need to avoid the same thing happens again, i.e, spending 2 years to
> > release a major version...
> agreed!
>
> On 2018/05/07 00:52:07, 张铎(Duo Zhang) <palomino...@gmail.com> wrote:
> > As I volunteered to be the release manager for the 2.1 release line so
> let
> > me bring this up.
> >
> > For the 2.1 release line, I would like to define it as the 'real' 2.x
> > version of HBase. It should include the features which are reverted or
> > disabled from 2.0.0 release, for example, serial replication, and in
> memory
> > compaction. And also, the performance issues. And no more new features.
> If
> > no objections, I will start the release work soon.
> >
> > And for the 3.0.0 release, I think the new features should be decided
> ASAP.
> > We need to avoid the same thing happens again, i.e, spending 2 years to
> > release a major version...
> >
> > For now, the new features
> > Synchronous replication
> > CCSMap
> > Backup
> > Spark connector(is it still active?)
> >
> > And I suggest that we include this:
> > The read path refactoring(HBASE-20525)
> >
> > Suggestions are welcomed.
> >
> > Thanks.
> >
>

Reply via email to