You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2011/09/05 07:17:09 UTC

[jira] [Commented] (MAPREDUCE-2398) MRBench: setting the baseDir parameter has no effect

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

Harsh J commented on MAPREDUCE-2398:
------------------------------------

Michael,

Thanks for the patch! :)

One minor nit: Can "mr_input" and "mr_output" strings be constant-ized and reused across both setting statements?

For the test question, I think events outside code approach is better.

> MRBench: setting the baseDir parameter has no effect
> ----------------------------------------------------
>
>                 Key: MAPREDUCE-2398
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2398
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: benchmarks
>    Affects Versions: 0.20.2, 0.22.0
>            Reporter: Michael Noll
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-2398-trunk.patch, MAPREDUCE-2398_0.20.2.patch
>
>
> The optional {{-baseDir}} parameter lets user specify the base DFS path for output/input of MRBench.
> However, the two private variables {{INPUT_DIR}} and {{OUTPUT_DIR}} (MRBench.java) are not updated in the case that the default value of  {{-baseDir}} is actually overwritten by the user. Hence any input and output is always written to the default locations ({{/benchmarks/MRBench/...}}), even though the user-supplied location for {{-baseDir}} is created (and eventually deleted again) on HDFS.
> The bug affects at least Hadoop 0.20.2 and the current trunk (r1082703) as of March 21, 2011.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira