Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Sep 2016 13:48:20 +0000 (UTC)
From: "Rohith Sharma K S (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13001293.1472562035000.507775.1473256100835@Atlassian.JIRA>
In-Reply-To: <JIRA.13001293.1472562035000@Atlassian.JIRA>
References: <JIRA.13001293.1472562035000@Atlassian.JIRA> <JIRA.13001293.1472562035465@arcas>
Subject: [jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in
 REST endpoints
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Sep 2016 13:48:23 -0000


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

Rohith Sharma K S commented on YARN-5585:
-----------------------------------------

bq. fetch the specific entity mentioned in fromId using a HBase Get and get created time field for that entity ID.
Right, this was the first approach considered. And Li lu also suggested the same approach similar to ATS1.5 does. But problem is entities may not stored in their creation time order. Say, if entities are stored in a row *<EntityId-3, T1> <EntityId-1, T2>  <EntityId-2, T3>* then the above approach would fail. Because say fromId=Entity-2 expecting to get Entity-3 but createtime is T3 which empty rows are retrieved from HBase.  

> [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