[
https://issues.apache.org/jira/browse/HBASE-26817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503536#comment-17503536
]
Nick Dimiduk commented on HBASE-26817:
--------------------------------------
Should we apply the relationship in the inverse direction? I.e., there are a
couple subclasses of {{RpcExecutor}} that are marked as {{IA.Private}}. If the
visibility of their parent class is opened up, should theirs also be opened? I
advocate that yes they should so as to keep our compatibility guarantees as
simple to understand/enforce as possible.
See also conversation on https://github.com/apache/hbase/pull/4173
[~busbey], [~elserj], [~zhangduo], [~apurtell] thoughts?
> Mark RpcExecutor as IA.LimitedPrivate COPROC and PHOENIX
> --------------------------------------------------------
>
> Key: HBASE-26817
> URL: https://issues.apache.org/jira/browse/HBASE-26817
> Project: HBase
> Issue Type: Task
> Components: compatibility
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> {{RpcExecutor}}, an abstract base class, is marked as {{IA.Private}}.
> However, it has several subclasses that are marked as
> {{IA.LimitedPrivate(COPROC, PHOENIX)}}. I think that the base class needs to
> match the highest exposure level of any of its subclasses.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
