You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by James Taylor <ja...@apache.org> on 2016/02/03 01:07:27 UTC
blockers for 4.7.0?
Are PHOENIX-1769, PHOENIX-1973, or PHOENIX-2649 blockers for 4.7.0 release?
Re: blockers for 4.7.0?
Posted by Sergey Soldatov <se...@gmail.com>.
Please wait. Fix for PHOENIX-2649 doesn't work as expected. So, I
reopened it and attached a new fix. For PHOENIX-1973 there will be
some performance improvement and I need to retest it carefully with
applied PHOENIX-2649.
Thanks,
Sergey
On Wed, Feb 3, 2016 at 6:44 PM, James Taylor <ja...@apache.org> wrote:
> Ok, let's roll a new RC then. PHOENIX-2649 has a fix as do a few others.
> Let's see if we can get a fix in for PHOENIX-2647 before cutting a new RC.
> If PHOENIX-1973 is ready, that one is fine too IMHO.
>
> On Tue, Feb 2, 2016 at 11:56 PM, Gabriel Reid <ga...@gmail.com>
> wrote:
>
>> PHOENIX-1973 doesn't seem like a blocker to me, although it would
>> certainly be a good improvement.
>>
>> PHOENIX-2649 does look like a blocker however -- I think that the
>> potential issues for an incorrect WritableComparator in an MR job
>> could likely include doing the wrong thing if an OOME isn't triggered.
>>
>> - Gabriel
>>
>> On Wed, Feb 3, 2016 at 1:07 AM, James Taylor <ja...@apache.org>
>> wrote:
>> > Are PHOENIX-1769, PHOENIX-1973, or PHOENIX-2649 blockers for 4.7.0
>> release?
>>
Re: blockers for 4.7.0?
Posted by James Taylor <ja...@apache.org>.
Ok, let's roll a new RC then. PHOENIX-2649 has a fix as do a few others.
Let's see if we can get a fix in for PHOENIX-2647 before cutting a new RC.
If PHOENIX-1973 is ready, that one is fine too IMHO.
On Tue, Feb 2, 2016 at 11:56 PM, Gabriel Reid <ga...@gmail.com>
wrote:
> PHOENIX-1973 doesn't seem like a blocker to me, although it would
> certainly be a good improvement.
>
> PHOENIX-2649 does look like a blocker however -- I think that the
> potential issues for an incorrect WritableComparator in an MR job
> could likely include doing the wrong thing if an OOME isn't triggered.
>
> - Gabriel
>
> On Wed, Feb 3, 2016 at 1:07 AM, James Taylor <ja...@apache.org>
> wrote:
> > Are PHOENIX-1769, PHOENIX-1973, or PHOENIX-2649 blockers for 4.7.0
> release?
>
Re: blockers for 4.7.0?
Posted by Gabriel Reid <ga...@gmail.com>.
PHOENIX-1973 doesn't seem like a blocker to me, although it would
certainly be a good improvement.
PHOENIX-2649 does look like a blocker however -- I think that the
potential issues for an incorrect WritableComparator in an MR job
could likely include doing the wrong thing if an OOME isn't triggered.
- Gabriel
On Wed, Feb 3, 2016 at 1:07 AM, James Taylor <ja...@apache.org> wrote:
> Are PHOENIX-1769, PHOENIX-1973, or PHOENIX-2649 blockers for 4.7.0 release?
Re: blockers for 4.7.0?
Posted by "김영우 (YoungWoo Kim)" <yw...@apache.org>.
I believe PHOENIX-2659 is a blocker too.
Youngwoo
2016년 2월 3일 수요일, James Taylor<ja...@apache.org>님이 작성한 메시지:
> Are PHOENIX-1769, PHOENIX-1973, or PHOENIX-2649 blockers for 4.7.0 release?
>
Re: blockers for 4.7.0?
Posted by "김영우 (Youngwoo Kim)" <wa...@gmail.com>.
IMO, PHOENIX-2649 affects bulkloader's performance and scalibility. Would
be nice to have a fix in 4.7.0
Thanks,
Youngwoo
2016년 2월 3일 수요일, James Taylor<ja...@apache.org>님이 작성한 메시지:
> Are PHOENIX-1769, PHOENIX-1973, or PHOENIX-2649 blockers for 4.7.0 release?
>