[
https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421446#comment-15421446
]
Andrew Purtell commented on PHOENIX-3116:
-----------------------------------------
bq. Is it ok to add methods to public interfaces in patch releases?
Needs to be clarified. See http://hbase.apache.org/book.html#hbase.versioning
{blockquote}
"new APIs may be added which will not be available in earlier patch versions"
"Client code written to APIs available in a given patch release might not run
against the old jars from an earlier patch version."
"A patch upgrade is a drop-in replacement. Any change that is not Java binary
compatible would not be allowed.[1]. Downgrading versions within patch releases
may not be compatible."
{blockquote}
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
{blockquote}
"A minor upgrade requires no application/client code modification."
{blockquote}
implies source compatibility even on minor releases, which is not the intent I
think.
The compatibility matrix also suggests Evolving interfaces cannot be changed on
patch releases, which I can see as intended.
The guidelines do not address source compatibility specifically.
> 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)
