[
https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072061#comment-15072061
]
Li Lu commented on YARN-4224:
-----------------------------
I think it's still depending on if we would like to model entity type as one
stage of the location of the resource, rather than if a parameter is mandatory
or not. If we add entity type as a part of the end point, it mean that in our
system, user should locate an timeline entity through
.../app/app_id/entity_type/entity_id. I'm actually fine with adding this one
level, but my point is to make sure we're consistent on the location of this
resource (in everywhere of our REST APIs), not to just open a special case for
our HBase implementation. [~leftnoteasy]'s point on returning an error would
also work. It just leaves flexibility for future implementations.
BTW, I think adding -uid is a good idea to distinguish the two types of
endpoints.
> 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,
> YARN-4224-feature-YARN-2928.wip.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
