[
https://issues.apache.org/jira/browse/PHOENIX-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234562#comment-14234562
]
Andrew Purtell commented on PHOENIX-1501:
-----------------------------------------
Right, shims are another option. I don't like it personally because they're
hard to maintain, most devs will only use one or maybe two versions of a thing,
but could be added to the list in the description above as another last resort
or perhaps even the preferred option by consensus
> Remove or replace all uses of InterfaceAudience.Private HBase APIs and classes
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-1501
> URL: https://issues.apache.org/jira/browse/PHOENIX-1501
> Project: Phoenix
> Issue Type: Task
> Reporter: Andrew Purtell
>
> Umbrella issue for removing or replacing all uses of
> InterfaceAudience.Private HBase APIs and classes.
> We won't be in a sustainable position if we don't establish a support
> contract with HBase for use of its private internals - each major HBase
> release will trigger potentially significant Phoenix refactoring.
> Let's approach it on a case by case basis. We can ask HBase to make private
> APIs and classes supported by promoting their audience to
> LimitedPrivate(PHOENIX). If that fails, we can negotiate a supportable
> interface and contribute or assist in the necessary refactoring. If that
> fails, we can redesign or implement internal analogues. If that fails, we can
> go back to the HBase community with a stronger argument for the necessity of
> a supportable interface and prevail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
