[
https://issues.apache.org/jira/browse/YARN-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418113#comment-16418113
]
Gour Saha commented on YARN-8084:
---------------------------------
[~leftnoteasy] are you referring to changing api.records.Component to
ServiceComponent or service.component.Component? I am fine with prefixing the
classes (with name collision) under api.records with "Service". If we stick to
this style then renaming service.component.Component is not required since
there won't be name collision anymore.
> Yarn native service classes renaming for easier development?
> -------------------------------------------------------------
>
> Key: YARN-8084
> URL: https://issues.apache.org/jira/browse/YARN-8084
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Wangda Tan
> Priority: Major
>
> There're a couple of classes with same name exists in YARN native service.
> Such as:
> 1) ...service.component.Component and api.records.Component.
> This makes harder when development in IDE since clash of class name forces to
> use full qualified class name.
> Similarly in API definition:
> ...service.api.records:
> Container/ContainerState/Resource/ResourceInformation. How about rename them
> to:
> ServiceContainer/ServiceContainerState/ServiceResource/ServiceResourceInformation?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
