hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6677) InterfaceAudience.LimitedPrivate should take a string not an enum
Date Sun, 25 Apr 2010 21:37:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860769#action_12860769
] 

Jakob Homan commented on HADOOP-6677:
-------------------------------------

I'm OK with the switch to strings; it'll make the annotation more useful to other projects,
as Alan said, and it's not like we have any real control over someone else using the APIs.
My concern is more about the possibility of making it optional; For LimitedPrivate, in Hadoop
at least, we should always be clear about who we're including. Making the list of targets
optional would make LimitedPrivate just a confusing version of Private.

> InterfaceAudience.LimitedPrivate should take a string not an enum
> -----------------------------------------------------------------
>
>                 Key: HADOOP-6677
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6677
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Alan Gates
>            Assignee: Tom White
>            Priority: Minor
>         Attachments: HADOOP-6677.patch
>
>
> Trying to keep the list of all possible components sharing limited private interfaces
up to date is painful.  As other subprojects beyond HDFS and MR use this interface it will
only get worse (see PIG-1311).  If it is converted to a string other subprojects can use it
without requiring patches to common.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message