The Phoenix Team is pleased to announce the immediate release of Apache Phoenix
4.8.2.
Download it from your favorite Apache mirror [1].
Apache Phoenix 4.8.2 a bug fix release for the Phoenix 4.8 release line,
compatible with Apache HBase 0.98, 1.0, 1.1 & 1.2.
This release fixes the following 2
The vote passed with 3 +1's, no 0 or -1. We will release 4.8.2RC2 as Phoenix
4.8.2
From: Thomas D'Silva
To: dev@phoenix.apache.org
Sent: Wednesday, November 23, 2016 7:23 PM
Subject: Re: [VOTE] Release of Apache Phoenix 4.8.2 RC2
+1
Ran integration tests. Ran some manual tests fo
Yeah... Sorry *very* busy. Will call the vote, do the release, and announce.
-- Lars
From: Josh Elser
To: dev@phoenix.apache.org
Sent: Thursday, December 1, 2016 12:53 PM
Subject: Re: [VOTE] Release of Apache Phoenix 4.8.2 RC2
Hey Lars,
Is a +1 from yourself to be implied here (if n
Hello Fellow Phoenix'ers,
The third RC for Apache Phoenix 4.8.2 is available. This is a patch release for
the Phoenix 4.8 release line,
compatible with Apache HBase 0.98, 1.0, 1.1 & 1.2.
This release fixes the following 26 issues:
[PHOENIX-2996] - Process name of PQS should indicate its role
From: "la...@apache.org"
To: Dev
Sent: Monday, November 7, 2016 1:31 PM
Subject: [VOTE] Release of Apache Phoenix 4.8.2 RC1
Hello Fellow Phoenix'ers,
The second RC for Apache Phoenix 4.8.2 is available. This is a patch release
for the Phoenix 4.8 release line,
compatible with Ap
If this is not a new issue introduced with 4.8.2. it does not necessarily have
to sink the release, it'd just get fixed next month.
This seems bad, though, so I agree.
-- Lars
From: James Taylor
To: "dev@phoenix.apache.org" ; lars hofhansl
Sent: Wednesday, November 9, 2016 10:04 AM
S
Hello Fellow Phoenix'ers,
The second RC for Apache Phoenix 4.8.2 is available. This is a patch release
for the Phoenix 4.8 release line,
compatible with Apache HBase 0.98, 1.0, 1.1 & 1.2.
This release fixes the following 17 issues:
[PHOENIX-2996] - Process name of PQS should indicate its rol
Due to PHOENIX-3439
Will spin a new release tomorrow.
From: "la...@apache.org"
To: Dev
Sent: Friday, November 4, 2016 1:53 PM
Subject: [VOTE] Release of Apache Phoenix 4.8.2 RC0
Hello Fellow Phoenix'ers,
The first RC for Apache Phoenix 4.8.2 is available. This is a patch release f
Hello Fellow Phoenix'ers,
The first RC for Apache Phoenix 4.8.2 is available. This is a patch release for
the Phoenix 4.8 release line,
compatible with Apache HBase 0.98, 1.0, 1.1 & 1.2.
This release fixes the following 17 issues:
[PHOENIX-2996] - Process name of PQS should indicate its role
Great. 14 fixes in a patch release. That's a healthy number.
Andy, didn't react to your earlier offer... Did you want to do the 4.8.2
release? Fine either way.
-- Lars
From: Samarth Jain
To: dev ; la...@apache.org
Sent: Wednesday, November 2, 2016 3:31 PM
Subject: Re: 4.8.2 and/or 4.9.
Need to wait PHOENIX-3432 in both branches.
From: "la...@apache.org"
To: "dev@phoenix.apache.org"
Sent: Wednesday, November 2, 2016 3:27 PM
Subject: Re: 4.8.2 and/or 4.9.0
I'll clean up Jira for 4.8.2 and spin the RCs. Today and/or early tomorrow.
From: James Taylor
To: "d
I'll clean up Jira for 4.8.2 and spin the RCs. Today and/or early tomorrow.
From: James Taylor
To: "dev@phoenix.apache.org"
Cc: lars hofhansl
Sent: Wednesday, November 2, 2016 3:00 PM
Subject: Re: 4.8.2 and/or 4.9.0
I'm in support of 4.8.2. I was just pointing out that we've alrea
Was going to do it this week. Then again, since 4.9.0 does not include the
column encoding I was less enthused about it.If we think we want a 4.8.2 I'll
spin an RC today.
-- Lars
From: Andrew Purtell
To: "dev@phoenix.apache.org"
Cc: lars hofhansl
Sent: Wednesday, November 2, 2016 11:
Hi All,
we have 20 jiras against 4.8.2 some of which seem important enough ... and over
200 against 4.9.0.
I think we should start keeping stable branches for longer.As before I'll
volunteer doing 4.8.2 as well as a 4.9.0.
Let's think about a 4.8.2 in two weeks or so, unless there're vastly diffe
The Phoenix Team is pleased to announce the immediate release of Apache Phoenix
4.8.1.
Download it from your favorite Apache mirror [1].
Apache Phoenix 4.8.1 a bug fix release for the Phoenix 4.8 release line,
compatible with Apache HBase 0.98, 1.0, 1.1 & 1.2.
This release fixes the following 4
With 4 +1's (including mine) and no -1 the vote passes.I will release RC0 as
Phoenix 4.8.1
On to 4.8.2 and/or 4.9.0 :)
-- Lars
From: James Taylor
To: "dev@phoenix.apache.org" ; lars hofhansl
Sent: Monday, September 26, 2016 3:54 PM
Subject: Re: [VOTE] The first rc (RC0) for Phoenix 4.
My key is the KEYS file in the dev directory only.
Will load into KEYS file you mention.
My key's fingerprint is A1A7 5143 64FB 05BC C9A1 5A9D D0BE B8C5 C7CF E328.
-- Lars
From: Josh Elser
To: dev@phoenix.apache.org
Sent: Friday, September 23, 2016 2:48 PM
Subject: Re: [VOTE] The first
Hello Fellow Phoenix'ers,
The first RC for Apache Phoenix 4.8.1 is available. This is a patch release for
the Phoenix 4.8 release line,
compatible with Apache HBase 0.98, 1.0, 1.1 & 1.2.
This release fixes the following 43 issues:
[PHOENIX-1367] - VIEW derived from another VIEW doesn't use p
And thanks to everybody who committed some of their jiras since my last email.
-- Lars
From: "la...@apache.org"
To: "dev@phoenix.apache.org"
Sent: Thursday, September 8, 2016 2:00 PM
Subject: Re: Starting to think about 4.8.1
I committed my two outstanding issues, and made a pass t
I committed my two outstanding issues, and made a pass through the jira and
pushed some to 4.8.2.
18 issues are still assigned to 4.8.1, please have a look. I'll do another more
aggressive pass early next week.
-- Lars
From: "la...@apache.org"
To: "dev@phoenix.apache.org" ; "la...@apach
I meant: "It would be great if everybody could go through their jira's and push
issues they won't get to within 10 days to 4.8.2 OR unschedule those from 4.8,
to mark them as 4.9 only".
Also, please make sure that jira is up to date. If a fix was committed to the
4.x/master and the 4.8 branches
I'd like to have an RC out within 10 days, to start a regular monthly cadence.
Just checked jira. There are 21 items fixed, and 30 items either open or
patch-available.I'll do a pass through all the open issues. It would be great
if everybody could go through their jira's and push issue they won
I think we need to keep 1.0 for 4.8.x.
From: James Taylor
To: "dev@phoenix.apache.org" ; lars hofhansl
Sent: Friday, August 26, 2016 11:06 AM
Subject: Re: [DISCUSS] Drop HBase 1.0 support for 4.9
What about 4.8-1.0? Will we drop that as well or will we do patch releases
for 1.0?
R.I.P. 4.x-1.0. It's toast.
From: "la...@apache.org"
To: "dev@phoenix.apache.org"
Sent: Tuesday, August 23, 2016 8:59 PM
Subject: Re: [DISCUSS] Drop HBase 1.0 support for 4.9
I'll take this as a vote. If you feel we need an "official" vote thread, speak
up now.If I do not hear any
RIP 4.x-1.0. It's toast.
From: "la...@apache.org"
To: "dev@phoenix.apache.org"
Sent: Tuesday, August 23, 2016 8:59 PM
Subject: Re: [DISCUSS] Drop HBase 1.0 support for 4.9
I'll take this as a vote. If you feel we need an "official" vote thread, speak
up now.If I do not hear anythi
I'll take this as a vote. If you feel we need an "official" vote thread, speak
up now.If I do not hear anything I'll remove the 4.x-1.0 branch in the next few
days.
Thanks.
-- Lars
From: Josh Elser
To: dev@phoenix.apache.org
Sent: Monday, August 22, 2016 7:54 AM
Subject: Re: [DISCUSS
Thanks Josh.
Just to be clear, I did not mean that all issues should be assigned to 4.9.0
and 4.8.1, but only those issues that represent minor and backwards compatible
fixes. (I know you know this, but for the sake of others).
-- Lars
From: Josh Elser
To: dev@phoenix.apache.org
Sent:
Hi All,
as we're two active branches right now, it is important to remember (1) that
fixes are pushed to both 4.8xxx and 4.x branches and (2) that the jiras are
marked as such, i.e. with 4.8.1 and 4.9.0.
Also, there are currently 129 unresolved jiras against 4.9.0.It would be great
if folks go
The HBase 1.0.x branch has been EOL'd, I propose we drop support for it with
Phoenix 4.9.I'd also propose that should HBase have a stable 1.3.x release
soon, we should support it with Phoenix 4.9.
-- Lars
Thanks John.
How was the region server Java process' heap configured?(Mujtaba is out today,
not sure he'll listen in before Monday)
On our regular SKUs we configure the region servers with 31GB of heap (the
machines have more RAM than that), but I am not sure about which test cluster
we used fo
I think Stack it trying to help and was just asking whether Mujtaba did
something special to load the data (and perhaps how it took for us and on how
many nodes we did that).(If it loaded fine for us and there was nothing special
we had to do, I agree that there's no way (or need) to troubleshoo
Great. Can somebody make me an administrator for Phoenix in Jira?I am for HBase
but not for Phoenix.
-- Lars
From: James Taylor
To: "dev@phoenix.apache.org" ; lars hofhansl
Sent: Tuesday, August 16, 2016 10:45 AM
Subject: Re: [DISCUSS] RM for next release
Thanks, Lars. I don't thi
Should we put this up for a vote?
There are a few "conditions" that need to be met, IMHO, to be successful with a
monthly release cadence.
1. Ability to skip releases. When we do monthly releases we can not expect user
to follow along. So it has to be possible to upgrade straight from (say) 4.8.0
+1
- Built from source- Did various tests, including perf- looks all good.
Let's get this sucker out.
From: Ankit Singhal
To: dev@phoenix.apache.org
Sent: Sunday, August 7, 2016 2:19 AM
Subject: [VOTE] Release of Apache Phoenix 4.8.0 RC2
Hello Everyone,
This is a call for a vote on
Not a show-stopper by itself, IMHO.But see PHOENIX-3156, which is a
show-stopper. Might as well pull PHOENIX-3149 in.
-- Lars
From: James Taylor
To: "dev@phoenix.apache.org"
Sent: Friday, August 5, 2016 4:30 PM
Subject: is PHOENIX-3149 a showstopper?
Or is it something we can addr
I have a fix. Please review. Then we should spin a new RC.
From: "la...@apache.org"
To: "dev@phoenix.apache.org"
Sent: Friday, August 5, 2016 7:50 PM
Subject: Re: [VOTE] Release of Apache Phoenix 4.8.0 RC1
-1
Sorry. See PHOENIX-3156. My doing.
-- Lars
From: Ankit Singhal
T
-1
Sorry. See PHOENIX-3156. My doing.
-- Lars
From: Ankit Singhal
To: dev@phoenix.apache.org
Sent: Wednesday, August 3, 2016 3:28 AM
Subject: [VOTE] Release of Apache Phoenix 4.8.0 RC1
Hello Everyone,
This is a call for a vote on Apache Phoenix 4.8.0 RC1. This is the next
minor rel
What I do to allow commit even while running the tests is to create a tag in
tag and then run jenkins against that tag instead of a branch.
-- Lars
From: Ankit Singhal
To: dev@phoenix.apache.org
Sent: Wednesday, August 3, 2016 1:35 AM
Subject: Re: new 4.8.0 RC?
Yeah. Let's cut RC
Also, can we branch 4.8-x in git?That way bigger changes can still go into the
4.x branches, while bugs are fixed in 4.8-x branches.
-- Lars
From: James Taylor
To: "dev@phoenix.apache.org"
Sent: Thursday, July 21, 2016 7:16 PM
Subject: new 4.8.0 RC?
How about a cutting a new RC no
+1 (binding).
Compiled from source. Loaded about 100m rows, queried, flushed, compacted, etc.
Retested all the features that I added.
Looks all good, nothing undue in the logs.
From: Ankit Singhal
To: dev@phoenix.apache.org
Sent: Wednesday, July 13, 2016 9:54 PM
Subject: [VOTE] Release
0.94 never took that much time from me.Sure some days it's a lot of work, but
on average I found it a task that can be easily done on the side.
I relied a lot on the Apache Jenkins, triggering runs and checking back the
next day, etc.I also think you're more diligent in your RM duties :)
-- Lars
+1 on 4.8.x should support HBase 1.0. (although it would safe us maintenance of
For 4.9 we can drop that (but likely should pull in support for HBase
1.3).We'll need to continue with 0.98 support until 0.98 is EOL'd, I think.
I'm happy to do 4.8.1 and 4.9 for one release, to confirm Stack's nick
I assigned PHOENIX-3056 to 4.8.0, just so we won't lose track of it. If it's
not an issue we can move to 4.9.
From: James Taylor
To: "dev@phoenix.apache.org" ; Mujtaba Chohan
Sent: Thursday, July 7, 2016 1:24 AM
Subject: Re: where are we at with the RC?
@Ankit, @Mujtaba - where a
Agreed. On all counts.
There are some bigger changes in the pipeline (column remapping and "dense"
column storage).Those are powerful and combine the power of SQL and HBase quite
nicely. I propose we get those soon after 4.8 and then spin a 4.9 from those.
A 4.8.1 would be of great value as well
Oh as you know, I am a very big fan of clearly defined patch/minor/major
compatibility.I'd love to have something like what we now have for HBase for
Phoenix as well. (could view it as debt paid forward if we want to really
consider merging the PMCs :) )
-- Lars
From: Nick Dimiduk
To:
All good discussions.
IMHO what matters most initially is to get more frequent and smaller releases.
The effect is a more steady commit stream, more stable releases, and earlier
access to bugfixes (and features) for users.
The patch/minor cadence will likely emerge a function of that, we'll see h
I think I have a fix for PHOENIX-2724, that seems important to get it.
-- Lars
From: Ankit Singhal
To: James Taylor
Cc: "dev@phoenix.apache.org" ; Samarth Jain
; Rajeshbabu Chintaguntla
; Thomas D'Silva ;
Mujtaba Chohan
Sent: Saturday, July 2, 2016 11:03 AM
Subject: Re: where are w
OK... If you guys agree, I'll volunteer, and shoot for a 4.9 (or 4.8.1, or 5.0,
whatever we decide to name it) release one month after 4.8.(The one
complicating factor... I will be traveling a bit this coming month).
-- Lars
From: James Taylor
To: "dev@phoenix.apache.org" ; "la...@apache.
Hi all,
This reminds me a bit of the HBase times before we went to a more or less
strict monthly release train.
It was harder to stabilize a release and there were lots of last minutes
changes and fixes, just because each release was big (in terms of the number of
changes).In addition folks wer
PHOENIX-3037 (Andy just committed) needs to get in.
-- Lars
From: Samarth Jain
To: dev
Cc: Ankit Singhal
Sent: Tuesday, June 28, 2016 9:58 AM
Subject: Re: where are we at with the RC?
PHOENIX-3028 is in. PHOENIX-2724 is a blocker as of now. Will work on this
today to see if it is j
Bit belated... For what's it worth, I'm fine either way.
I'd be leaning towards 5.0, since forcing synchronized client and server
upgraded for any feature is tricky for many organizations.The new major version
number would be a warning flag.
Or phrased differently, if this does not warrant 5.0,
PHOENIX-3014, PHOENIX-3012 have been pushed. Good to go on those.
From: James Taylor
To: "dev@phoenix.apache.org"
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 reviewe
I built phoenix-0.4.7-0.98 from source and I am trying start tephra.
I added
data.tx.snapshot.dir
/tmp/tephra/snapshots
data.tx.timeout
60
To the server's hbase-site.xml and export HBASE_HOME to point the HBase
install. I double and triple checked this.
Yet, regardl
And turns out I also need to remove the pherf jars from Phoenix's lib dir.I
think we change the tephra script to automatically not include those.
-- Lars
From: "la...@apache.org"
To: "dev@phoenix.apache.org" ; "la...@apache.org"
Sent: Friday, March 18, 2016 10:37 PM
Subject: Re: Teph
Gr. Some of the -test jars that ship with the Phoenix build contain an
hbase-site.xml and hence the settings are lost.If I remove all the test jars
things are fine.
So it seems I cannot run tephra against a tar that built myself, unless I
remove all the -test jars.
Then I tried the official
55 matches
Mail list logo
