Re: RC for 4.11.0 by end of week?

[James Taylor <ja...@apache.org>]

Unless anyone knows of any outstanding, required JIRAs for 4.11.0, I think
we're ready for an RC.

Thanks,
James

On Wed, May 31, 2017 at 2:28 PM, Samarth Jain <sa...@gmail.com>
wrote:

> I would like to get a fix for
> https://issues.apache.org/jira/browse/PHOENIX-3836 in too. Taking a look
> at
> it right now.
>
> On Wed, May 31, 2017 at 1:37 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > https://issues.apache.org/jira/browse/PHOENIX-3891 would be nice to get
> > in. If a user runs into this, things would blow up fairly quickly :).
> Test
> > provided, just needs a review.
> >
> > Let me get a patch up for 3895.
> >
> >
> > On 5/30/17 8:07 PM, James Taylor wrote:
> >
> >> We've got a bunch of good bug fixes in our 4.x branches *and* we have
> >> support for HBase 1.3 which is great. How about we shoot for an RC by
> the
> >> end of the week? Here's a few JIRAs that we can potentially include:
> >>
> >> Must Haves
> >> ----------------
> >> PHOENIX-3797 Local Index - Compaction fails on table with local index
> due
> >> to non-increasing bloom keys
> >> PHOENIX-3870 Backward compatibility fails between v4.9.0 and head of 4.x
> >> PHOENIX-3896 Fix test failures related to tracing changes
> >>
> >> Nice to Haves
> >> -------------------
> >> PHOENIX-3819 Reduce Phoenix load on RS hosting SYSTEM.CATALOG region
> >> PHOENIX-3815 Only disable indexes on which write failures occurred
> >> PHOENIX-3895 Update to Apache Calcite Avatica 1.10.0
> >> PHOENIX-3773 Implement FIRST_VALUES aggregate function
> >> PHOENIX-3612 Make tracking of max allowed number of mutations bytes
> based
> >> instead of row based
> >>
> >> Is there other pending work we should consider for 4.11.0?
> >>
> >> Thanks,
> >> James
> >>
> >>
>

Re: RC for 4.11.0 by end of week?

["rajeshbabu@apache.org" <ch...@gmail.com>]

Hi James,

Ankit pointed this PHOENIX-3898. Looking into it. Seems very bad bug.

Thanks,
Rajeshbabu.

On Thu, Jun 8, 2017 at 3:07 PM, James Taylor <ja...@apache.org> wrote:

> Unless anyone knows of any outstanding, required JIRAs for 4.11.0, I think
> we're ready for an RC.
>
> Thanks,
> James
>
> On Wed, May 31, 2017 at 2:28 PM, Samarth Jain <sa...@gmail.com>
> wrote:
>
> > I would like to get a fix for
> > https://issues.apache.org/jira/browse/PHOENIX-3836 in too. Taking a look
> > at
> > it right now.
> >
> > On Wed, May 31, 2017 at 1:37 PM, Josh Elser <jo...@gmail.com>
> wrote:
> >
> > > https://issues.apache.org/jira/browse/PHOENIX-3891 would be nice to
> get
> > > in. If a user runs into this, things would blow up fairly quickly :).
> > Test
> > > provided, just needs a review.
> > >
> > > Let me get a patch up for 3895.
> > >
> > >
> > > On 5/30/17 8:07 PM, James Taylor wrote:
> > >
> > >> We've got a bunch of good bug fixes in our 4.x branches *and* we have
> > >> support for HBase 1.3 which is great. How about we shoot for an RC by
> > the
> > >> end of the week? Here's a few JIRAs that we can potentially include:
> > >>
> > >> Must Haves
> > >> ----------------
> > >> PHOENIX-3797 Local Index - Compaction fails on table with local index
> > due
> > >> to non-increasing bloom keys
> > >> PHOENIX-3870 Backward compatibility fails between v4.9.0 and head of
> 4.x
> > >> PHOENIX-3896 Fix test failures related to tracing changes
> > >>
> > >> Nice to Haves
> > >> -------------------
> > >> PHOENIX-3819 Reduce Phoenix load on RS hosting SYSTEM.CATALOG region
> > >> PHOENIX-3815 Only disable indexes on which write failures occurred
> > >> PHOENIX-3895 Update to Apache Calcite Avatica 1.10.0
> > >> PHOENIX-3773 Implement FIRST_VALUES aggregate function
> > >> PHOENIX-3612 Make tracking of max allowed number of mutations bytes
> > based
> > >> instead of row based
> > >>
> > >> Is there other pending work we should consider for 4.11.0?
> > >>
> > >> Thanks,
> > >> James
> > >>
> > >>
> >
>