Where can we take the parcel for CDH 5.11.x from ?

 

From: Kumar Palaniappan [mailto:kpalaniappan@marinsoftware.com]
Sent: Monday, November 27, 2017 10:51 AM
To: user@phoenix.apache.org
Subject: Re: [ANNOUNCE] Apache Phoenix 4.13 released

 

You mean CDH5.9 and 5.10? And also HBASE 17587?

 

On Mon, Nov 27, 2017 at 12:37 AM, Pedro Boado <pedro.boado@gmail.com> wrote:

My branch is based on 4.x-HBase. But I wouldn't recommend using cdh4.9 & 4.10 as they include HBASE-16604 but not it's fix HBASE-17187 (issue found in PHOENIX-3736)

 

Cheers. 

 

On 27 Nov 2017 08:28, "Kumar Palaniappan" <kpalaniappan@marinsoftware.com> wrote:

Thanks @james.

 

Since this patch(Phoenix-4372) is tightly coupled with CDH5.11.2, would like to get the 4.13HBase1.2 branch released so can make it compatible with CDH5.9.2 the version which our clusters are on and test.

 

@Pedro, please let me know, how to get access to 4.13.1HBase1.2

 

On Fri, Nov 24, 2017 at 10:08 AM, James Taylor <jamestaylor@apache.org> wrote:

@Kumar - yes, we’ll do a 4.13.1 release shortly for HBase 1.2 out of the head of the 4.x-HBase-1.2 branch. Pedro is going to be the RM going forward for this branch and do CDH release from this. You can track that on PHOENIX-4372.

 

@Flavio - Pedro is targeting a CDH 5.11.2 release. 

 

On Fri, Nov 24, 2017 at 8:53 AM Flavio Pompermaier <pompermaier@okkam.it> wrote:

Hi to all, 

is there any Parcel available for Phoenix 4.13 and Cloudera CDH 5.9-5.10 available (HBase 1.2) somewhere?

 

Best,

Flavio

 

On Thu, Nov 23, 2017 at 7:33 AM, Kumar Palaniappan <kpalaniappan@marinsoftware.com> wrote:

@Jmaes, are you still planning to release 4.13HBase1.2?

 

On Sun, Nov 19, 2017 at 1:21 PM, James Taylor <jamestaylor@apache.org> wrote:

Hi Kumar,

I started a discussion [1][2] on the dev list to find an RM for the HBase 1.2 (and HBase 1.1) branch, but no one initially stepped up, so there were no plans for a release. Subsequently we've heard from a few folks that they needed it, and Pedro Boado volunteered to do CDH compatible release (see PHOENIX-4372) which requires an up to date HBase 1.2 based release.

 

So I've volunteered to do one more Phoenix 4.13.1 release for HBase 1.2 and 1.1. I'm hoping you, Pedro and others that need 1.2 based releases can volunteer to be the RM and do further releases.

 

One thing is clear, though - folks need to be on the dev and user lists so they can take place in DISCUSS threads.

 

Thanks,

James

 

 

On Sun, Nov 19, 2017 at 12:23 PM, Kumar Palaniappan <kpalaniappan@marinsoftware.com> wrote:

Are there any plans to release Phoenix 4.13 compatible with HBase 1.2?

 

On Sat, Nov 11, 2017 at 5:57 PM, James Taylor <jamestaylor@apache.org> wrote:

The Apache Phoenix team is pleased to announce the immediate availability of the 4.13.0 release. Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop using Apache HBase as its backing store and providing integration with other projects in the Apache ecosystem such as Spark, Hive, Pig, Flume, and MapReduce. The 4.x releases are compatible with HBase 0.98 and 1.3.

 

Highlights of the release include:

 

* Critical bug fix to prevent snapshot creation of SYSTEM.CATALOG when connecting [1]

* Numerous bug fixes around handling of row deletion [2]

* Improvements to statistics collection [3] 

* New COLLATION_KEY built-in function for linguistic sort [4]

 

Source and binary downloads are available here [5].

 

 

 

 



 

--

Flavio Pompermaier
Development Department

OKKAM S.r.l.
Tel. +(39) 0461 041809

 

 




PRIVILEGED AND CONFIDENTIAL
PLEASE NOTE: The information contained in this message is privileged and confidential, and is intended only for the use of the individual to whom it is addressed and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, or if any problems occur with transmission, please contact sender. Thank you.