phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: [DISCUSS] Road to HBase 2.0.0
Date Fri, 27 Oct 2017 18:40:07 GMT
Just had an offlist chat with Sergey, Rajeshbabu, and Ankit.

FYI you all will probably see a branch show up soon which includes the 
necessary HBase 2.0 changes (the work primarily outlined in 
PHOENIX-4297). This branch will probably be in a flux for a while 
(questionable states of compilation/test-failure).

I wanted to make sure that folks who had the time/interest to contribute 
to the not-so-fun effort were able to ;). Will share a branch name when 
I see it.

On 10/11/17 6:00 PM, Josh Elser wrote:
> Since 4.12.0 is out and we have the concurrent discussions about the 
> 0.98, 1.1, and 1.2 HBase branches, do folks have a vision of how we get 
> to HBase 2.0.0?
> The lack of chatter is pretty obvious that the Calcite work (the 
> previous impetus for Phoenix 5) has slowed. Once we get to an HBase 
> 2.0.0-alpha4, coprocessor API should stabilize and give us a point 
> against which we can start Phoenix work.
> Should a release of Phoenix that supports HBase 2.0 be worthy of the 
> Phoenix 5.0 label, or should we stick to the 4.x numbering? Given the 
> breaking changes going into HBase 2.0 and James' previous -1 to 
> shim-layers for 0.98, do we see the same for an HBase 2.0 branch or is 
> HBase 1.x/2.x a different beast? I can see pros/cons for both sides.
> - Josh

View raw message