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] [Updated] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints
Date Tue, 04 Oct 2016 14:19:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rohith Sharma K S updated YARN-5585:
------------------------------------
    Attachment: 0001-YARN-5585.patch

Updating the patch with following changes for early review
# Added *idPrefix* in TimelineEntity object.

Collector Implementation:
# id_prefix is been published as row-key and as column to HBase.

Reader Implementation:
# entityPrefixId is part of TimelineReaderContext.
# Along with entityPrefixId, fromId is also supported. Difference is entityPrefixId applied
at storage level, and fromId is applied at reader side.
# Removed sortedKey variable.
# Used LinkedHashSet instead of TreeSet while adding entities to Set.
# startRow and stopRow is calculated dynamically based on entityPrefixId existence. 

Pending Task.
# Need to add queryParams in REST end points from entityPrefixId and fromId
# For single entity retrieval, need to use SingleColumnFileter for retrieval. 
# Need to test in real cluster

> [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: 0001-YARN-5585.patch, 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
(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