[
https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523177#comment-15523177
]
Varun Saxena edited comment on YARN-5585 at 9/26/16 2:13 PM:
-------------------------------------------------------------
bq. 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?
Entity ID prefix will be supplied by Tez in your case, while publishing
entities, and can be inverse of created time if you want rows to be sorted in a
descending order by created time. TimelineEntity class will now carry a prefix
too.
bq. Does new tables separate or same-existing?
Same tables. Just the row key changes if you are not happy with lexicographic
order.
was (Author: varun_saxena):
bq. 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?
Entity ID prefix will be supplied by Tez in your case and can be inverse of
created time if you want rows to be sorted in a descending order by created
time. TimelineEntity class will now carry a prefix too.
bq. Does new tables separate or same-existing?
Same tables. Just the row key changes if you are not happy with lexicographic
order.
> [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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
