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 Wed, 05 Jun 2013 00:20:21 GMT

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

Sanjay Radia commented on HADOOP-9517:

bq.  ... Optional fields can be added any time .. Fields can be renamed any time ...

This is what stable means. Hence i suggest that we add a comment to the .proto files to say
that the .protos are private-stable, and we could add the comment on kinds of changes allowed.
Will file a jira for this. Given that are no annotations for .proto, a comment is the best
that can be done.

bq. Don't you think the proto files for client interfaces should be public? I was chatting
with Todd about this, and it seems to us they should.
I would still mark it as private till we make the rpc and data transfer protocol itself public
(ie the protos being public is useless without the rpc proto being public. 
Todd and I occasionally disagree ;-)

> 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, hadoop-9517-v2.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

View raw message