[ https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhao, Qingwen updated EAGLE-467: -------------------------------- Description: Job search rest api: /rest/mrJobs/search?jobId=?&site=? QueryParam: jobId & site Return: job list api: /rest/mrJobs?query=%s[@site=?]{*}&pageSize=100000&startTime=2016-08-10%2006:25:51&endTime=2016-08-10%2008:25:51 task count statistic api: /rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo×=0,30,60&top=3 The problem is current we store running jobs and historic jobs into different places, which presents an obstacle when we want to query all jobs regardless of the status. was: Job search rest api: /rest/mrJobs/search?jobId=?&site=? job list api: /rest/mrJobs?query=%s[@site=?]{*}&pageSize=100000&startTime=2016-08-10%2006:25:51&endTime=2016-08-10%2008:25:51 The problem is current we store running jobs and historic jobs into different places, which presents an obstacle when we want to query all jobs regardless of the status. > Add job query apis for both running & historic jobs > ---------------------------------------------------- > > Key: EAGLE-467 > URL: https://issues.apache.org/jira/browse/EAGLE-467 > Project: Eagle > Issue Type: New Feature > Reporter: Zhao, Qingwen > Assignee: Zhao, Qingwen > > Job search rest api: > /rest/mrJobs/search?jobId=?&site=? > QueryParam: jobId & site > Return: > job list api: > /rest/mrJobs?query=%s[@site=?]{*}&pageSize=100000&startTime=2016-08-10%2006:25:51&endTime=2016-08-10%2008:25:51 > task count statistic api: > /rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo×=0,30,60&top=3 > The problem is current we store running jobs and historic jobs into different > places, which presents an obstacle when we want to query all jobs regardless > of the status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)