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

Hadoop QA commented on YARN-1838:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12635874/YARN-1838.2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new 
or modified test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3423//console

This message is automatically generated.

> Timeline service getEntities API should provide ability to get entities from 
> given id
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-1838
>                 URL: https://issues.apache.org/jira/browse/YARN-1838
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Srimanth Gunturi
>            Assignee: Billie Rinaldi
>         Attachments: YARN-1838.1.patch, YARN-1838.2.patch
>
>
> To support pagination, we need ability to get entities from a certain ID by 
> providing a new param called {{fromid}}.
> For example on a page of 10 jobs, our first call will be like
> [http://server:8188/ws/v1/timeline/HIVE_QUERY_ID?fields=events,primaryfilters,otherinfo&limit=11]
> When user hits next, we would like to call
> [http://server:8188/ws/v1/timeline/HIVE_QUERY_ID?fields=events,primaryfilters,otherinfo&fromid=JID11&limit=11]
> and continue on for further _Next_ clicks
> On hitting back, we will make similar calls for previous items
> [http://server:8188/ws/v1/timeline/HIVE_QUERY_ID?fields=events,primaryfilters,otherinfo&fromid=JID1&limit=11]
> {{fromid}} should be inclusive of the id given.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to