[
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-467.
-------------------------------
Resolution: Done
> 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=?
> /rest/mrJobs/search?jobDefId=?&site=?
> Description: search all jobs by jobId or jobDefId
> QueryParam: jobId/jobIdId & site
> Return: job list with both running/historic jobs with no duplicate ones
> *Job list api*
> /rest/mrJobs?query=%s[@site=?]{*}&pageSize=100000&startTime=2016-08-10%2006:25:51&endTime=2016-08-10%2008:25:51
> Description: show all jobs in a site
> QueryParam: site
> Return: job list with both running/historic jobs with no duplicate ones
> *Task count statistic api*
> /rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo×=0,30,60&top=3
> Description: return running/finished tasks with the task count value and top
> longest task set in each time slot
> QueryParam: site & timeslot list (seconds)
> Return:
> 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)