hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17725) LimitedPrivate COPROC / PHOENIX interface broken on maintenance release
Date Fri, 03 Mar 2017 20:47:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895001#comment-15895001
] 

Sean Busbey commented on HBASE-17725:
-------------------------------------

[VOTE thread for 1.1.8|https://lists.apache.org/thread.html/18127e20750955d91dae8d6a079c4814a18600dd73a41bbff7d82159@%3Cdev.hbase.apache.org%3E],
both [~ndimiduk] and I said the change looked fine.

I think this means probably things are fine as is. I'll try to ping phoenix for impact so
we have a better idea on how likely this is to break downstream coprocessor writers.

> LimitedPrivate COPROC / PHOENIX interface broken on maintenance release
> -----------------------------------------------------------------------
>
>                 Key: HBASE-17725
>                 URL: https://issues.apache.org/jira/browse/HBASE-17725
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 1.2.5, 1.1.8
>            Reporter: Sean Busbey
>            Priority: Blocker
>             Fix For: 1.2.5
>
>         Attachments: 1.2.4_1.2.5RC0_compat_report.html
>
>
> The compatibility report for HBase 1.2.5 RC0 flagged one item, the interface {{RpcServiceInterface}}
added a new method {{setRsRpcServices}}. That interface is labeled {{IA.LimitedPrivate(COPROC,
PHOENIX)}}.
> AFAICT this change came in on HBASE-16972. There's discussion on that ticket about the
compatibility impact of the change in logging on earlier releases (which I remain fine with).
The only discussion about binary/source compatibility expressly changes a different part of
the patch to avoid breaking coprocessors and phoenix.
> As an extra wrinkle, this change has already been published in the 1.1.z release line
for 1.1.8 and 1.1.9. Apologies, but I haven't gone to verify there wasn't a discussion of
this break when 1.1.8 came out.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message