[
https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453109#comment-15453109
]
Varun Saxena commented on YARN-5585:
------------------------------------
bq. Can we translate the fromId request into some HBase filters
Yes, for fetching apps within flow run, we can set the start row in HBase scan
to achieve this. Application ID part in Application table rowkey is stored as
12 bytes (inverted cluster timestamp of 8 bytes and inverted sequence number of
4 bytes). So within the scope of flow run, we can set fromId as application ID
bit while specifying start row in HBase scan.
For getting apps within a flow, in addition to app id (received from fromId),
we can specify flow run id as inverted value of max value of long i.e. 0. And
set this as start row in HBase scan. This would require comparatively more
matches but should be fine as we will doing row key prefix match.
> [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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
