[
https://issues.apache.org/jira/browse/YARN-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419903#comment-16419903
]
Gour Saha commented on YARN-8084:
---------------------------------
[~eyang], I agree with you. I would also prefer if existing classes in
api.records remain as is, primarily because it is end-user/consumer friendly.
By consumers, I primarily refer to the REST API or programmatic client-side API
users who would use the swagger definition to generate client-side stubs in a
language of their choice. The duplication of class name is definitely
inconvenient for developers, but I prefer developers taking the hit rather than
consumers. Nevertheless, if we rename the non-(api.records) classes we will
solve the dev issue as well.
> 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]
