[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189633#comment-13189633
 ] 

Amar Kamat commented on MAPREDUCE-3597:
---------------------------------------

Few questions:
1. You have added a new {{getQueueName()}} API to {{JobSubmittedEvent}} class. 
Can you add some test case or validation lines for this newly added API?
2. Is there a testcase testing the map/reduce job level counters? As I 
understand, these counters got added recently and not available in the test 
logs. Is it possible to run a MR job (or reuse logs from other test scenarios) 
for the same?
3. Is it possible for the conf entires (e.g. queue name etc) to be null? Is it 
safe to check for nullity before setting the field in Parsed/LoggedTask from 
the conf?

                
> Provide a way to access other info of history file from Rumentool
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-3597
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3597
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: tools/rumen
>    Affects Versions: 0.24.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.24.0
>
>         Attachments: 3597.branch-1.v1.patch, 3597.branch-1.v2.patch, 
> 3597.v0.patch, 3597.v1.patch
>
>
> As the trace file generated by Rumen TraceBuilder is skipping some of the 
> info like job counters, task counters, etc. we need a way to access "other 
> info available in history file which is not dumped to trace file". This is 
> useful for components which want to parse history files and get info. These 
> components can directly use/leverage "Rumen's parsing of history files across 
> hadoop releases" and get history info in a consistent way for further 
> analysis/processing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to