[
https://issues.apache.org/jira/browse/MAPREDUCE-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926201#action_12926201
]
Ravi Gummadi commented on MAPREDUCE-2151:
-----------------------------------------
>>I do not follow your first part. For the second part (exclusion list), it
>>will add significant complexity (now the order of the list may matter). I
>>suggest we wait until some concrete usage case emerge.
I didn't go through the match() method earlier. But what I wanted to give as
input is something like "mapreduce.job." as the prefix and get all the config
properties that start with "mapreduce.job." into the trace file. I think it can
be done. Let me see your next patch which adds an option to TraceBuiler and see
if anything is missing from my expectations.
I agree that it may be complex to support exclusion list with StringTrie. Let
us see that case later if that case is really important.
> [rumen] Add a map of jobconf key-value pairs in LoggedJob
> ---------------------------------------------------------
>
> Key: MAPREDUCE-2151
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2151
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: tools/rumen
> Reporter: Hong Tang
> Assignee: Hong Tang
> Attachments: mr-2151-yhadoop-20.201.patch
>
>
> It'd be useful to retain application level configuration settings in
> LoggedJob.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
