Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 8 Sep 2016 05:30:20 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13001293.1472562035000.516432.1473312620714@Atlassian.JIRA>
In-Reply-To: <JIRA.13001293.1472562035000@Atlassian.JIRA>
References: <JIRA.13001293.1472562035000@Atlassian.JIRA> <JIRA.13001293.1472562035465@arcas>
Subject: [jira] [Comment Edited] (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: Thu, 08 Sep 2016 05:30:23 -0000


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

Varun Saxena edited comment on YARN-5585 at 9/8/16 5:29 AM:
------------------------------------------------------------

IIUC, Tez DAG ID is a combination of YARN App ID and DAG sequence ID.
Isnt this DAG sequence ID monotonically increasing and assigned to DAGs' as they are run and assigned to them in sequence ?
I was assuming they were. That is why I suggested storing DAG ID as 16 bytes (8 bytes of inverted cluster timsetamp from app id +  4 bytes of inverted seq id from app id + 4 bytes of inverted DAG seq number). Padding in this case wont be required.

Anyways other solutions have been proposed and we can come back to this only if necessary.
Or maybe we can have both above solution and below one as well.


was (Author: varun_saxena):
IIUC, Tez DAG ID is a combination of YARN App ID and DAG sequence ID.
Isnt this DAG sequence ID monotonically increasing and assigned to DAGs' as they are run in sequence ?
I was assuming they were. That is why I suggested storing DAG ID as 16 bytes (8 bytes of inverted cluster timsetamp from app id +  4 bytes of inverted seq id from app id + 4 bytes of inverted DAG seq number). Padding in this case wont be required.

Anyways other solutions have been proposed and we can come back to this only if necessary.
Or maybe we can have both above solution and below one as well.

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