lt;mailto:user@phoenix.apache.org>"
> <user@phoenix.apache.org <mailto:user@phoenix.apache.org>>
> 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
ly-To: "user@phoenix.apache.org<mailto:user@phoenix.apache.org>"
<user@phoenix.apache.org<mailto:user@phoenix.apache.org>>
Date: Friday, 10 June 2016 at 9:06 AM
To: "user@phoenix.apache.org<mailto:user@phoenix.apache.org>"
<user@phoenix.apache.org<mailto:user
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 (https://phoenix.apache.org/upgrading.html)
"Phoenix maintains backward compatibility across at least two minor releases
Pick the tree for your CDH 5.x version and it should all work. We are missing
trees for X=6 and X=7 and I will aim to get to that soon.
I did not test beyond insuring all Phoenix unit and integration tests passed.
> On Jun 9, 2016, at 7:55 PM, Benjamin Kim wrote:
>
>
> is cloudera's hbase 1.2.0-cdh5.7.0 that different from apache HBase 1.2.0?
Yes
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:
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
https://issues.apache.org/jira/browse/PHOENIX-2834. I could get it to build,
but I
Koert,
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
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