phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ankur Jain <>
Subject Re: phoenix on non-apache hbase
Date Fri, 10 Jun 2016 05:09:14 GMT
I have updated my jira with updated instructions

Please do let me know if you are able to build and use with CDH5.7

Ankur Jain

From: Andrew Purtell <<>>
Reply-To: "<>" <<>>
Date: Friday, 10 June 2016 at 9:06 AM
To: "<>" <<>>
Subject: Re: phoenix on non-apache hbase

Yes a stock client should work with a server modified for CDH assuming both client and server
versions are within the bounds specified by the backwards compatibility policy (

"Phoenix maintains backward compatibility across at least two minor releases to allow for
no downtime through server-side rolling restarts upon upgrading."

On Jun 9, 2016, at 8:09 PM, Koert Kuipers <<>>

is phoenix client also affect by this? or does phoenix server isolate the client?

is it reasonable to expect a "stock" phoenix client to work against a custom phoenix server
for cdh 5.x? (with of course the phoenix client and server having same phoenix version).

On Thu, Jun 9, 2016 at 10:55 PM, Benjamin Kim <<>>

Since we are still on CDH 5.5.2, can I just use your custom version? Phoenix is one of the
reasons that we are blocked from upgrading to CDH 5.7.1. Thus, CDH 5.7.1 is only on our test
cluster. One of our developers wants to try out the Phoenix Spark plugin. Did you try it out
in yours too? Does it work if you did?


On Jun 9, 2016, at 7:47 PM, Andrew Purtell <<>>

>  is cloudera's hbase 1.2.0-cdh5.7.0 that different from apache HBase 1.2.0?


As is the Cloudera HBase in 5.6, 5.5, 5.4, ... quite different from Apache HBase in coprocessor
and RPC internal extension APIs.

We have made some ports of Apache Phoenix releases to CDH here:<>

It's a personal project of mine, not something supported by the community. Sounds like I should
look at what to do with CDH 5.6 and 5.7.

On Jun 9, 2016, at 7:37 PM, Benjamin Kim <<>>

This interests me too. I asked Cloudera in their community forums a while back but got no
answer on this. I hope they don't leave us out in the cold. I tried building it too before
with the instructions here I could get
it to build, but I couldn't get it to work using the Phoenix installation instructions. For
some reason, dropping the server jar into CDH 5.7.0 HBase lib directory didn't change things.
HBase seemed not to use it. Now that this is out, I'll give it another try hoping that there
is a way. If anyone has any leads to help, please let me know.


On Jun 9, 2016, at 6:39 PM, Josh Elser <<>>


Apache Phoenix goes through a lot of work to provide multiple versions of Phoenix for various
versions of Apache HBase (0.98, 1.1, and 1.2 presently). The builds for each of these branches
are tested against those specific versions of HBase, so I doubt that there are issues between
Apache Phoenix and the corresponding version of Apache HBase.

In general, I believe older versions of Phoenix clients can work against newer versions of
Phoenix running in HBase; but, of course, you'd be much better off using equivalent versions
on both client and server.

If you are having issues running Apache Phoenix over vendor-creations of HBase, I would encourage
you to reach out on said-vendor's support channels.

- Josh

Koert Kuipers wrote:
hello all,

i decided i wanted to give phoenix a try on our cdh 5.7.0 cluster. so i
download phoenix, see that the master is already for hbase 1.2.0, change
the hbase version to 1.2.0-cdh5.7.0, and tell maven to run tests make
the package, expecting not much trouble.

but i was wrong... plenty of compilation errors, and some serious
incompatibilities (tetra?).

yikes. what happened? why is it so hard to compile for a distro's hbase?
i do this all the time for vendor-specific hadoop versions without
issues. is cloudera's hbase 1.2.0-cdh5.7.0 that different from apache
hbase 1.2.0?

assuming i get the phoenix-server working for hbase 1.2.0-cdh5.7.0, how
sensitive is the phoenix-client to the hbase version? can i at least
assume all the pain is in the phoenix-server and i can ship a generic
phoenix-client with my software that works on all clusters with the same
phoenix-server version installed?

thanks! best, koert

View raw message