You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2017/11/14 10:38:00 UTC

[jira] [Commented] (HBASE-19254) Write up how InterfaceAudience works over class hierarchy

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

Anoop Sam John commented on HBASE-19254:
----------------------------------------

+1 on [~chia7712] suggestion.  

> Write up how InterfaceAudience works over class hierarchy
> ---------------------------------------------------------
>
>                 Key: HBASE-19254
>                 URL: https://issues.apache.org/jira/browse/HBASE-19254
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>            Reporter: stack
>
> Over on the tail of HBASE-19235, there is a discussion around marking classes with InterfaceAudicence in a hierarchy. One camp suggests that it could be possible that a super class might be IA.Private but subclasses (and their methods) could then be IA.LP. General opinion held the opposite. [~chia7712] said it best:
> bq. It makes sense to me that sub-class can always narrow the declaration (ex. IA.Public -> IA.Private/IA.LP). Widening the declaration is like a issue we need to fix.....
> This issue is about adding a note to the IA section in refguide (should probably pass it by dev list before it goes into refguide).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)