Hi Flavio

Thanks for the quick respond it is helpful.
According to your answer, if I will upgrade my cluster to CDH 5.11.2 it will 
work. This is what I am understanding.

Regards,
Dor

From: Flavio Pompermaier [mailto:[email protected]]
Sent: יום ה 28 דצמבר 2017 10:06
To: [email protected]
Subject: Re: Phoenix and Cloudera

I don't think it wiĺl work on Cloudera 5.10.1
There are 2 Phoenix parcel: the last official one (Phoenix 4.7 on cdh 4.9) and 
the unofficial one (under release) that is Phoenix 4.13 on CDH 5.11.2.
You can find more info at
http://community.cloudera.com/t5/Cloudera-Labs/Apache-Phoenix-Support-for-CDH-5-8-x-5-9x-5-10-x-5-11-x/m-p/62687#M416?eid=1&aid=1

Best,
Flavio

On 28 Dec 2017 08:29, "Dor Ben Dov" 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

I am trying with no luck due to many exceptions to connect phoenix to CDH 5.10.1
Can one give some tips, guidance how it should be done ?

I tried with the manual on the Apache site as well as via Cloudera Parcels 
distribution and activation process.

Regards,
Dor Ben Dov
Research Manager, Digital – BSS - Research
+972-9-7764043<tel:+972%209-776-4043>   (office)
+972-52-3573492<tel:+972%2052-357-3492> (mobile)
[cid:[email protected]]

Follow us on Facebook<http://www.facebook.com/amdocs/>, 
Twitter<http://twitter.com/amdocs>, 
LinkedIn<http://www.linkedin.com/company/amdocs>, 
YouTube<http://www.youtube.com/amdocsinc>, 
Google+<https://plus.google.com/105657940751678445194> and the Amdocs blog 
network<http://blogs.amdocs.com/>| Digital BSS 
Research@Yammer<https://www.yammer.com/amdocs.com/#/threads/inGroup?type=in_group&feedId=7043838>

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

Reply via email to