You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2014/10/22 23:23:33 UTC
[jira] [Created] (MAPREDUCE-6134) Add entity-level info or primary
filters to facilitate job history data query
Zhijie Shen created MAPREDUCE-6134:
--------------------------------------
Summary: Add entity-level info or primary filters to facilitate job history data query
Key: MAPREDUCE-6134
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6134
Project: Hadoop Map/Reduce
Issue Type: Sub-task
Components: jobhistoryserver
Reporter: Zhijie Shen
Per discussion in [MAPREDUCE-5933|https://issues.apache.org/jira/browse/MAPREDUCE-5933?focusedCommentId=14180283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14180283], we may need to add some properties in the events to MR job or task entity's otherInfo or primaryFilter to support some particular query.
For example, getting all the tasks of one MR job:
{code}
http://localhost:8188/ws/v1/timeline/MAPREDUCE_TASK?primaryFilter=PARENT_JOB:job_1413998833197_0001
{code}
By adding \{PARENT_JOB:job_1413998833197_0001\} to the primary filter of each task entity of job_1413998833197_0001 is going to significantly shorten the time to search the target task entities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)