hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4536) MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
Date Wed, 29 Oct 2008 06:10:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643419#action_12643419
] 

Alejandro Abdelnur commented on HADOOP-4536:
--------------------------------------------

In the {{run}} method, the line:

{code}
        jc.set("mapred.local.dir", "build/test/mapred/local");
{code}

should be changed to:

{code}
        jc.set("mapred.local.dir", System.getProperty("test.build.mapred", "build/test/mapred/local"));
{code}

Thus  preserving the current behavior but allowing to change it via a system property.


> MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4536
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4536
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: test
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Minor
>
> The {{mapred.local.dir}} configuration property for the {{MiniMRCluster}} is forced to
{{build/test/mapred/local}}
> This is inconvenient in different situations. For example:
> * When running multiple tests using {{MiniMRCluster}} is not possible to see the end
state of the dir for a particular test
> * When using {{MiniMRCluster}} in another build system (i.e. Maven) that uses a different
output directory (target instead build)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message