hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9517) Document Hadoop Compatibility
Date Fri, 31 May 2013 21:01:21 GMT

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

Sanjay Radia commented on HADOOP-9517:
--------------------------------------

bq. Shouldn't the proto files themselves be classified as public and stable?
If you mean the wire protocol proto files, then no. They are not public as we have not made
the protocol itself public; we may do that at some point and at that time we would make them
public. At this stage we have merely promised to maintain wire compatibility going forward.
Right now the proto files should be marked as private-stable.
                
> Document Hadoop Compatibility
> -----------------------------
>
>                 Key: HADOOP-9517
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9517
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Arun C Murthy
>            Assignee: Karthik Kambatla
>         Attachments: hadoop-9517.patch, hadoop-9517.patch, hadoop-9517.patch, hadoop-9517.patch,
hadoop-9517-proposal-v1.patch, hadoop-9517-proposal-v1.patch
>
>
> As we get ready to call hadoop-2 stable we need to better define 'Hadoop Compatibility'.
> http://wiki.apache.org/hadoop/Compatibility is a start, let's document requirements clearly
and completely.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message