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/
Thanks James!
On Wed, Oct 18, 2017 at 3:52 PM, James Taylor
wrote:
> FYI, I filed JIRAs for the Phoenix changes we talked about in the
> spreadsheet and labeled them all with HBase-2.0 [1].
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%
> 20resolution%20%3D%2
FYI, I filed JIRAs for the Phoenix changes we talked about in the
spreadsheet and labeled them all with HBase-2.0 [1].
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%3D%22HBase-2.0%22
On Wed, Oct 18, 2017 at 3:38 PM, Sta
On Wed, Oct 18, 2017 at 12:13 PM, Josh Elser wrote:
>
> On 10/18/17 2:51 PM, Andrew Purtell wrote:
>
>> Hopefully, Phoenix will not find itself in a position where
>>>
>> business-critical things it's doing are being removed from API (and
>> Phoenix
>> has no recourse to hack what it needs back i
On 10/18/17 2:51 PM, Andrew Purtell wrote:
Hopefully, Phoenix will not find itself in a position where
business-critical things it's doing are being removed from API (and Phoenix
has no recourse to hack what it needs back in place).
I feel fairly confident this is going to happen given the rad
> Hopefully, Phoenix will not find itself in a position where
business-critical things it's doing are being removed from API (and Phoenix
has no recourse to hack what it needs back in place).
I feel fairly confident this is going to happen given the radical excision
of methods from the interfaces.
Yes, the earlier the better, but this is also a bit chicken-and-egg.
It's tough down in Phoenix to make sure it still works if the API we're
trying to write against is still changing.
I know that Anoop from the HBase side has been peering into the Phoenix
side -- I've been operating under the
Some notes on this effort:
+ Perhaps this discussion should be cc'd to dev@hbase? There is a good bit
of overlap between dev-set here and dev-set on hbase and some
interest/concern around Phoenix on HBase2.
+ Here are some notes I took after looking at Phoenix last week that I ran
by James off-lis
+1 James' plan is similar to what I had in mind. I think the quicker we
can get a branch in place to build against HBase2, the quicker we can
find and fix all of these rough edges.
Great list you have here, Sergey. Will certainly be helpful.
Ankit/Rajeshbabu, did you guys have anything to add
There is a list of problems that we need to fix to get it working with
HBase 2.0:
1. renamed methods (such as add => addColumn). That's the easiest to fix
2. removed interfaces such as HTableInterface. We are supposed to use Table
now. That may lead to some small difference between branches. Becaus
One idea of where to put the code:
- switch to using non deprecated HBase methods in master
- same for Tephra
- create a 5.0-HBase-2.0 branch to put code specific to getting Phoenix to
work against HBase 2.0
- take a look at the changes and see if a shim layer makes sense (I'm only
-1 on an HBase 0
Thanks, Anoop!
I know Sergey, Ankit, and Rajeshbabu have been looking at this already.
While tracking it is good, I think we still need to come up with a plan
for where we're going to put that new code in Phoenix :)
On 10/13/17 6:58 AM, Anoop John wrote:
Thanks for bringing this up. I was a
Thanks for bringing this up. I was abt to ask this. Ya the CP
framework itself and the CP exposed interfaces (Like
RegionServerServices, Region etc) are undergoing a big change for for
HBase 2.0.. I did a look at some of the usages of the Phoenix
exposed interfaces/classes. There are some item
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
14 matches
Mail list logo
