Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
MIME-Version: 1.0
In-Reply-To: <51914b1e-ab97-34eb-ac4c-66efdd6e1ad5@gmail.com>
References: <CAAF1Jdit2=hjJyoYwm=RuxD8Gc9n4DtSN=Ke3Hcuq7idtWFrPQ@mail.gmail.com>
 <51914b1e-ab97-34eb-ac4c-66efdd6e1ad5@gmail.com>
From: Samarth Jain <samarth.jain@gmail.com>
Date: Wed, 31 May 2017 14:28:59 -0700
Message-ID: <CAMfSBKJV7uEtgw6s3syHEaFzpnQwZTSGmD=U83oSyFyjKEFKpw@mail.gmail.com>
Subject: Re: RC for 4.11.0 by end of week?
To: dev <dev@phoenix.apache.org>
Content-Type: multipart/alternative; boundary="f403045ddf60c6f6c40550d89b80"
archived-at: Wed, 31 May 2017 21:29:05 -0000

--f403045ddf60c6f6c40550d89b80
Content-Type: text/plain; charset="UTF-8"

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 <josh.elser@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
>>
>>

--f403045ddf60c6f6c40550d89b80--