[
https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573206#comment-13573206
]
Vinod Kumar Vavilapalli commented on YARN-387:
----------------------------------------------
I propose we do the following conversions:
Main protocols:
- client_RM_protocol.proto -> client_rm_protocol.proto
- AM_RM_protocol.proto - > am_rm_protocol.proto
- container_manager.proto -> am_nm_protocol.proto
- ResourceTracker.proto -> rm_nm_protocol.proto
- LocalizationProtocol.proto -> nm_localizer_protocol.proto
- RMAdminProtocol.proto -> rm_admin_protocol.proto
Misc:
- yarnprototunnelrpc.proto -> yarn_rpc_tunnel_protos.proto
In addition, we should
- similarly rename all the java API classes backing the above protocols
- add comments to all the proto files description as to what they do and can
contain.
Thoughts?
> Fix inconsistent protocol naming
> --------------------------------
>
> Key: YARN-387
> URL: https://issues.apache.org/jira/browse/YARN-387
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> We now have different and inconsistent naming schemes for various protocols.
> It was hard to explain to users, mainly in direct interactions at
> talks/presentations and user group meetings, with such naming.
> We should fix these before we go beta.
--
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
