phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-1199) Determine options for Phoenix 4.1.x supporting CDH 5.1
Date Sat, 23 Aug 2014 19:00:11 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-1199:
----------------------------------

    Attachment: PHOENIX-1199.patch

Remove sole place in which Phoenix attempts to instantiate ServerName directly.

> Determine options for Phoenix 4.1.x supporting CDH 5.1 
> -------------------------------------------------------
>
>                 Key: PHOENIX-1199
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1199
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1
>            Reporter: James Taylor
>         Attachments: PHOENIX-1199.patch
>
>
> Let's figure out the most painless way of supporting CDH 5.1 for Phoenix 4.1. I'm not
as concerned with compile-time, as we know we have a dependency on HBase 0.98.4 (to fix a
deadlock issue). However, this is not a runtime dependency. But the lack of the ServerName
is going to be a problem at runtime. Are there other problematic class references?
> What are our options? Should we try to get something in the next HBase release that'll
help (making constructors public, for example)? Or can we not use ServerName in the Phoenix
code? Are the old HBase APIs available still? You all would know better than me.
> Or should we just wait for the next patch release from Cloudera and ask nicely that they
make it more compatible? smile :-)
> [~apurtell], [~stack], [~lhofhansl], [~jesse_yates]



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message