[
https://issues.apache.org/jira/browse/YARN-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418268#comment-16418268
]
Eric Yang commented on YARN-8084:
---------------------------------
[~leftnoteasy], I agree with Gour Saha that service.component.Component can be
renamed to ComponentManager for clarity. I am unsure about prefix Service in
service.api.records. The existing form is easier to read in my opinion. This
is the same as List class can come from many packages, and user can hover over
to see their origin in IDE.
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
