[
https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421461#comment-15421461
]
Josh Elser commented on PHOENIX-3116:
-------------------------------------
Argh.
bq. The above would seem to allow the Table API change under discussion here,
because it is binary compatible per the Java binary compat specification. Yet
This is my general understanding. HBase's compatibility statement is *not* what
is outlined at semver.org. Instead, it's more to do with binary compatibility
of the artifacts. As such, adding a method to an interface wouldn't break the
binary compatibility (of the caller) which is probably how we got here. I feel
like the intent is from a caller, not so much someone extending or implementing
the API.
Let me try to take this up in HBase land and see what others think there. By
the current state of the guidelines, I believe this change was allowed;
however, I do not like the current state of the guidelines :)
> Upgrade HBase dependency to 1.2.2
> ---------------------------------
>
> Key: PHOENIX-3116
> URL: https://issues.apache.org/jira/browse/PHOENIX-3116
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.8.0
> Reporter: Rob Leidle
> Assignee: James Taylor
> Priority: Minor
> Fix For: 4.8.1
>
> Attachments: upgrade-hbase-to-1.2.2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> HBase 1.2.2 made a backwards incompatible change in HTableInterface that
> requires new overrides.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
