Can we also get PHOENIX-3015 in 4.8? If someone review it I would be really
appreciated.

Thanks,
Sergey

On Tue, Jun 21, 2016 at 9:22 PM, Ankit Singhal <[email protected]>
wrote:

> Thanks James and Lars.
> Now we are waiting on two issues:-
>
> PHOENIX-3002
> PHOENIX-3020
>
> It seems both have fixes ready , probably will be committed by tomorrow.
>
> Regards,
> Ankit Singhal
>
> On Tue, Jun 21, 2016 at 7:04 PM, <[email protected]> wrote:
>
> > PHOENIX-3014, PHOENIX-3012 have been pushed. Good to go on those.
> >
> >       From: James Taylor <[email protected]>
> >  To: "[email protected]" <[email protected]>
> >  Sent: Tuesday, June 21, 2016 8:40 AM
> >  Subject: Re: RC on Monday
> >
> > A couple more to get in: PHOENIX-3014, PHOENIX-3012, PHOENIX-3013. Two of
> > these have already been reviewed and just need someone to commit them.
> >
> > Thanks,
> > James
> >
> > On Monday, June 20, 2016, Josh Elser <[email protected]> wrote:
> >
> > > I just realized I still have PHOENIX-2792 outstanding (was waiting on
> > > Avatica 1.8.0 and then forgot about it).
> > >
> > > I will put that in tonight so you can do the RC first thing tmrw
> morning,
> > > Ankit.
> > >
> > > Sorry for causing more delay.
> > >
> > > [email protected] wrote:
> > >
> > >> I can commit both PHOENIX-3002 and PHOENIX-2209 by today.
> > >>
> > >> It would be better to make RC tomorrow.
> > >>
> > >> Thanks,
> > >> Rajeshbabu.
> > >>
> > >> On Tue, Jun 21, 2016 at 7:24 AM, James Taylor<[email protected]>
> > >> wrote:
> > >>
> > >> Fixes for both PHOENIX-3001 and PHOENIX-2940 have been checked in
> > (thanks
> > >>> -
> > >>> nice work!). Looks like the only two outstanding are PHOENIX-3002 and
> > >>> PHOENIX-2209.
> > >>>
> > >>> Anything else missing? Can we get an RC up tomorrow (Tuesday)?
> > >>>
> > >>> Thanks,
> > >>> James
> > >>>
> > >>>
> > >>>
> > >>> On Thu, Jun 16, 2016 at 1:06 PM, Ankit Singhal<[email protected]>
> > wrote:
> > >>>
> > >>> Hi All,
> > >>>>
> > >>>> Changing the date for RC on Monday instead of Today. As following
> > JIRAs
> > >>>> still needs to get in.
> > >>>>
> > >>>> PHOENIX-3001(NPE during split on table with deleted local Indexes.
> > >>>>
> > >>>> PHOENIX-2940(Remove Stats RPC from meta table build lock)
> > >>>>
> > >>>> Regards,
> > >>>> Ankit Singhal
> > >>>>
> > >>>> On Tue, Jun 14, 2016 at 10:51 PM, Ankit Singhal<
> > >>>>
> > >>> [email protected]>
> > >>>
> > >>>> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>>
> > >>>>> As now the Jiras which needs to go in 4.8 are either done or have
> +1s
> > >>>>>
> > >>>> on
> > >>>
> > >>>> them. so how about having RC by Thursday EOD?
> > >>>>>
> > >>>>> Checked with Rajesh too , PHOENIX-1734 is also ready for 4.x
> branches
> > >>>>>
> > >>>> and
> > >>>
> > >>>> will be committed by tomorrow.
> > >>>>>
> > >>>>> Regards,
> > >>>>> Ankit Singhal
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Jun 1, 2016 at 12:33 PM, Nick Dimiduk<[email protected]>
> > >>>>>
> > >>>> wrote:
> > >>>>
> > >>>>> On Wed, Jun 1, 2016 at 10:58 AM, Josh Elser<[email protected]>
> > >>>>>>
> > >>>>> wrote:
> > >>>>
> > >>>>> I can try to help knock out some of those issues you mentioned as
> > >>>>>>>
> > >>>>>> well,
> > >>>>
> > >>>>> Nick.
> > >>>>>>>
> > >>>>>>
> > >>>>>> You mean my metacache woes? That's more than I'd hoped for!
> > >>>>>>
> > >>>>>> https://issues.apache.org/jira/browse/PHOENIX-2941
> > >>>>>> https://issues.apache.org/jira/browse/PHOENIX-2939
> > >>>>>> https://issues.apache.org/jira/browse/PHOENIX-2940
> > >>>>>> https://issues.apache.org/jira/browse/PHOENIX-2941
> > >>>>>>
> > >>>>>> :D
> > >>>>>>
> > >>>>>> James Taylor wrote:
> > >>>>>>
> > >>>>>>> Would be good to upgrade to Avatica 1.8 (PHOENIX-2960) - a vote
> > >>>>>>>>
> > >>>>>>> should
> > >>>>
> > >>>>> start on that today or tomorrow.
> > >>>>>>>>
> > >>>>>>>>      James
> > >>>>>>>>
> > >>>>>>>> On Tue, May 31, 2016 at 1:48 PM, Nick Dimiduk<
> [email protected]>
> > >>>>>>>>
> > >>>>>>> wrote:
> > >>>>>>
> > >>>>>>> We're hoping to get the shaded client jars [0] and rename of
> > >>>>>>>>
> > >>>>>>> queryserver
> > >>>>>>
> > >>>>>>> jar [1] changes in for 4.8. There's also an optimization
> > >>>>>>>>>
> > >>>>>>>> improvement
> > >>>
> > >>>> for
> > >>>>>>
> > >>>>>>> using skip scan that's close [2].
> > >>>>>>>>>
> > >>>>>>>>> [0]: https://issues.apache.org/jira/browse/PHOENIX-2535
> > >>>>>>>>> [1]: https://issues.apache.org/jira/browse/PHOENIX-2267
> > >>>>>>>>> [2]: https://issues.apache.org/jira/browse/PHOENIX-258
> > >>>>>>>>>
> > >>>>>>>>> On Tue, May 31, 2016 at 11:07 AM, Ankit Singhal<
> [email protected]
> > >
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>> Hello Everyone,
> > >>>>>>>>>
> > >>>>>>>>>> I'd like to propose a roll out of 4.8.0 RC early next
> week(*7th
> > >>>>>>>>>>
> > >>>>>>>>> June*)
> > >>>>>>
> > >>>>>>> Here is the list of some good work already been done for this
> > >>>>>>>>>>
> > >>>>>>>>> release.
> > >>>>>>
> > >>>>>>>      - Local Index improvements[1]
> > >>>>>>>>>>      - Phoenix hive integration[2]
> > >>>>>>>>>>      - Namespace mapping support[3]
> > >>>>>>>>>>      - Many VIEW enhancements[4]
> > >>>>>>>>>>      - Offset support for paging queries[5]
> > >>>>>>>>>>      - 50+ Bugs resolved[6]
> > >>>>>>>>>>      - Support for HBase v1.2
> > >>>>>>>>>>
> > >>>>>>>>>> What else we can get in ? Is there something being actively
> > >>>>>>>>>>
> > >>>>>>>>> worked
> > >>>
> > >>>> upon
> > >>>>>>
> > >>>>>>> but
> > >>>>>>>>>
> > >>>>>>>>> it will not be ready by proposed date?
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> Regards,
> > >>>>>>>>>> Ankit Singhal
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> [1] https://issues.apache.org/jira/browse/PHOENIX-1734
> > >>>>>>>>>> [2] https://issues.apache.org/jira/browse/PHOENIX-2743
> > >>>>>>>>>> [3] https://issues.apache.org/jira/browse/PHOENIX-1311
> > >>>>>>>>>> [4] https://issues.apache.org/jira/browse/PHOENIX-1508
> > >>>>>>>>>> [5] https://issues.apache.org/jira/browse/PHOENIX-2722
> > >>>>>>>>>> [6] https://issues.apache.org/jira/issues/?filter=12335812
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>
> > >>
> >
> >
> >
> >
>

Reply via email to