[
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424252#comment-15424252
]
ASF GitHub Bot commented on EAGLE-467:
--------------------------------------
Github user wujinhu commented on the issue:
https://github.com/apache/incubator-eagle/pull/348
The serialization/deserialization of
org.apache.eagle.jpm.mr.runningentity.JobConfig is a little complicated. Since
it is a java HashMap, should we consider to use java build-in
serialization/deserialization?
> 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=?
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
