[
https://issues.apache.org/jira/browse/MAPREDUCE-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranjit Mathew reassigned MAPREDUCE-1982:
----------------------------------------
Assignee: Ravi Gummadi
An example fragment is:
--------------------------------------- 8<
---------------------------------------
{
"priority" : "NORMAL",
"jobID" : "job_201007280625_0001",
"user" : "gridperf",
"jobName" : null,
"mapTasks" : [ {
"startTime" : 1280298532016,
"taskID" : "task_201007280625_0001_m_000323",
"taskType" : "MAP",
"attempts" : [ {
"location" : {
"layers" : [ "98\\.137\\.102\\.64",
"gsbl91438\\.blue\\.ygrid\\.yahoo\\.com" ]
},
"hostName" :
"/98\\.137\\.102\\.64/gsbl91438\\.blue\\.ygrid\\.yahoo\\.com",
"startTime" : 1280298532028,
"finishTime" : 1280298597501,
"result" : "SUCCESS",
--------------------------------------- 8<
---------------------------------------
This is because Rumen directly uses Properties instead of Configuration - the
new key-name is "mapreduce.job.name", while the old key-name was
"mapred.job.name". Using Configuration insulates against such changes.
> [Rumen] TraceBuilder's output shows jobname as NULL for jobhistory files with
> valid jobnames
> --------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1982
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1982
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tools/rumen
> Reporter: Amar Kamat
> Assignee: Ravi Gummadi
>
> {{TraceBuilder}} fails to extract configuration properties (like job-name)
> from the job-conf if the job-conf has the properties stored using the
> deprecated keys.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
