Looks like your fixes are all in, Josh - thanks for the quick turnaround!
Though there were a couple of IT failures in your test run, I've verified
locally that the tests all pass. So unless others have found any pending
showstoppers, I think we're good to proceed with the 4.9.0 RC.

Thanks,
James

On Mon, Oct 31, 2016 at 6:15 AM, Josh Elser <els...@apache.org> wrote:

> FYSA -- I'm doing this Avatica upgrade and pushing in PHOENIX-3004 now.
>
> James Taylor wrote:
>
>> Ok, thanks, Josh. We can hold off until Mon for the RC so we can get the
>> latest and greatest Avatica.
>>
>> On Fri, Oct 28, 2016 at 2:26 PM, Josh Elser<els...@apache.org>  wrote:
>>
>> Looks like Alan just voted, so it will pass once the 72hrs is up.
>>>
>>> I can make sure that change gets into Phoenix over the weekend.
>>>
>>>
>>> James Taylor wrote:
>>>
>>> If we can cut a Phoenix RC on Monday morning, it's likely still ok. Do
>>>> you
>>>> think the Avatica vote will close by Sun night (and yes, I'll vote :-)
>>>> )?
>>>>
>>>> Thanks,
>>>> James
>>>>
>>>> On Fri, Oct 28, 2016 at 8:08 AM, Josh Elser<els...@apache.org>   wrote:
>>>>
>>>> I wouldn't -1 4.9.0 over it since it's my own lack of time to have
>>>> gotten
>>>>
>>>>> out an Avatica release prior to this, but my feelings are best
>>>>> summarized
>>>>> by a -0. There aren't any show-stoppers, but 1.9.0 is a good
>>>>> "stabilizing"
>>>>> release upstream (I'm hoping that it will help drive more client-side
>>>>> work
>>>>> with PQS).
>>>>>
>>>>> If we're going to be sticking firmly to the schedule going forward
>>>>> (which
>>>>> is great, IMO), more than two days notice to the rc0 date would be
>>>>> appreciated :)
>>>>>
>>>>>
>>>>> James Taylor wrote:
>>>>>
>>>>> We'd like to stick to our schedule for a Phoenix 4.9.0 RC on Fri
>>>>> (10/28).
>>>>>
>>>>>> If there are no showstopper fixes in Avatica 1.9.0, are you ok with
>>>>>> getting
>>>>>> that in the next Phoenix release planned for one month from now, Josh?
>>>>>>
>>>>>> Thanks,
>>>>>> James
>>>>>>
>>>>>> On Wed, Oct 26, 2016 at 12:20 PM, Josh Elser<josh.el...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I'd like to get updated to Avatica 1.9.0 for Phoenix 4.9.0 (let's us
>>>>>> do
>>>>>>
>>>>>> PHOENIX-3004), but its vote is scheduled to close tmrw. That _should_
>>>>>>> give
>>>>>>> me time to push in the update and do some basic testing before
>>>>>>> Friday.
>>>>>>>
>>>>>>> Might I be able to sway you into casting a vote over there to make
>>>>>>> sure
>>>>>>> that the train of releases doesn't get held up, James? (Beers on me
>>>>>>> next
>>>>>>> time)
>>>>>>>
>>>>>>>
>>>>>>> James Taylor wrote:
>>>>>>>
>>>>>>> We've got a lot of great stuff (mostly bug fixes) already checked in
>>>>>>> for
>>>>>>>
>>>>>>> 4.9.0. Please let me know if you have any outstanding JIRAs you'd
>>>>>>>> like
>>>>>>>> to
>>>>>>>> see in the release. Here's a few that are under review and are
>>>>>>>> expected
>>>>>>>> to
>>>>>>>> make it in:
>>>>>>>> PHOENIX-6 Support ON DUPLICATE KEY construct
>>>>>>>> PHOENIX-476 Support declaration of DEFAULT in CREATE statement
>>>>>>>>
>>>>>>>> These will hopefully have a patch today and make it in too:
>>>>>>>> PHOENIX-3326 Restoring SYSTEM.CATALOG from snapshot causes clients
>>>>>>>> to
>>>>>>>> run
>>>>>>>> into UpgradeInProgressException
>>>>>>>> PHOENIX-3407 Wrong type of RowLock acquired by MetaDataEndPointImpl
>>>>>>>> for
>>>>>>>> HBase 1.2
>>>>>>>> PHOENIX-3396 Valid Multi-byte strings whose total byte size is
>>>>>>>> greater
>>>>>>>> than
>>>>>>>> the max char limit cannot be inserted into VARCHAR fields in the PK
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> James
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>

Reply via email to