hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints
Date Thu, 08 Sep 2016 02:50:22 GMT

    [ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472526#comment-15472526
] 

Varun Saxena commented on YARN-5585:
------------------------------------

bq. Just realized that a normal converter will not address the use case where users really
want entities sorted by their creation time
Yes, this is just for use cases where entity IDs' are structured in a manner where there is
direct correlation between entity ID and being sorted by creation time. DAG ID seems to be
generated same way. And seems to be the case in Spark too. If row keys are sorted that will
be the best solution from a performance perspective. However, there is that disadvantage of
putting the burden of it on the application to write some extra code and make sure that JARs'
are placed during deployment. That is why I asked if this will be acceptable to Tez.
On further thought though, we can also break ATS related behavior for the application if they
do choose to change their IDs' in a manner where its no longer sorted in future, however unlikely
that may be. 

Let me think of something else then.

> [Atsv2] Add a new filter fromId in REST endpoints
> -------------------------------------------------
>
>                 Key: YARN-5585
>                 URL: https://issues.apache.org/jira/browse/YARN-5585
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-5585.v0.patch
>
>
> TimelineReader REST API's provides lot of filters to retrieve the applications. Along
with those, it would be good to add new filter i.e fromId so that entities can be retrieved
after the fromId. 
> Example : If applications are stored database, app-1 app-2 ... app-10.
> *getApps?limit=5* gives app-1 to app-10. But to retrieve next 5 apps, it is difficult.
> So proposal is to have fromId in the filter like *getApps?limit=5&&fromId=app-5*
which gives list of apps from app-6 to app-10. 
> This is very useful for pagination in web UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message