hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9619) Mark stability of .proto files
Date Wed, 05 Jun 2013 00:26:20 GMT

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

Todd Lipcon commented on HADOOP-9619:
-------------------------------------

One thing I think we should clarify: I don't think the .proto files themselves should be stable.
Rather, the field IDs and types are stable -- ie we should not make any changes to the proto
files which cause wire incompatibility. But we should feel free to rename the .proto files
themselves, or change the annotations that affect code generation.

If a downstream project wants to use the Hadoop wire protocol, they should be making a _copy_
of the proto files for their use case, not assuming that we'll never rename a protobuf field
(which is wire-compatible).
                
> Mark stability of .proto files
> ------------------------------
>
>                 Key: HADOOP-9619
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9619
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Sanjay Radia
>            Assignee: Sanjay Radia
>


--
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