hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints
Date Mon, 26 Sep 2016 13:25:20 GMT

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

Rohith Sharma K S commented on YARN-5585:

Apologized,  I was in leave!! Lot more discussions are happened and trying to understand each
comments. One thing I would like to say is, lets design the system in general. Later can be
asked to tez or any other users to adopt to designed system with minimal changes. Tez publishes
entity id without padding, so lexicographical order goes toss for them!!.

# If {entityidprefix} is part of row-key then row-keys are sorted in lexicographical order.
When scan is performed on rows, the ResultScanner gives in the order of lexicographical order
only. I could not get where does this entityIdPrefix will be used? Is it from storage or readerservere?
# Limits on scanned rows can not be applied from HBase. So limit has to be taken care by readerServer.
I just attached work-around patch which I am using for testing purpose. 
# bq. We can have a separate REST endpoint to distinguish between prefix based queries and
non prefix based queries
Does new tables separate or same-existing? 

> [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
>            Priority: Critical
>         Attachments: YARN-5585-workaround.patch, 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. 
> Current Behavior : Default limit is set to 100. If there are 1000 entities then REST
call gives first/last 100 entities. How to retrieve next set of 100 entities i.e 101 to 200
OR 900 to 801?
> Example : If applications are stored database, app-1 app-2 ... app-10.
> *getApps?limit=5* gives app-1 to app-5. But to retrieve next 5 apps, there is no way
to achieve this. 
> 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. 
> Since ATS is targeting large number of entities storage, it is very common use case to
get next set of entities using fromId rather than querying all the entites. This is very useful
for pagination in web UI.

This message was sent by Atlassian JIRA

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

View raw message