[
https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059340#comment-15059340
]
Wangda Tan commented on YARN-4224:
----------------------------------
[~varun_saxena] thanks for reply.
bq. Now for entity endpoint we can then have UID from result of entities
endpoint. So entity type is not really required here. But should we have it for
sake of consistency ?
I would prefer to have a flat REST API for entities just like others.
If entity_type + entity_uid can uniquely locate a entity, why not directly add
the entity_type to entity_uid as well? Just like YARN's existing ids,
"container_" is the type of container object, and "application_" is the type of
application object. Is there any concern if you include entity_type to
entity_uid?
> Change the ATSv2 reader side REST interface to conform to current REST APIs'
> in YARN
> ------------------------------------------------------------------------------------
>
> Key: YARN-4224
> URL: https://issues.apache.org/jira/browse/YARN-4224
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Labels: yarn-2928-1st-milestone
> Attachments: YARN-4224-YARN-2928.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
