[
https://issues.apache.org/jira/browse/MAPREDUCE-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-6627:
-------------------------------------
Attachment: MAPREDUCE-6627.006.patch
The 006 patch renames the new files.
I spoke with Karthik offline and we agreed that for now, I'll just clarify the
CLI parsing with comments, and a followup JIRA to clean up all of the parsing
with a library will suffice. Trying to manually parse this one command for
now, and allowing it to be in any order, will be error prone (e.g. {{mapred job
-history foo.jhst -outfile all}}), and if we're going to redo it anyway with a
library, we may as well wait.
> Add machine-readable output to mapred job -history command
> ----------------------------------------------------------
>
> Key: MAPREDUCE-6627
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6627
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Affects Versions: 2.9.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-6627.001.patch, MAPREDUCE-6627.002.patch,
> MAPREDUCE-6627.003.patch, MAPREDUCE-6627.004.patch, MAPREDUCE-6627.005.patch,
> MAPREDUCE-6627.006.patch, json.txt, json_all.txt
>
>
> It would be great if we could add a machine-readable output format, say JSON,
> to the {{mapred job -history \[all\] <jobHistoryFile>}} command so that it's
> easier for programs to consume that information and do further processing on
> it. At the same time, we should keep the existing API and formatting intact
> for backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
