[jira] [Commented] (MAPREDUCE-2817) MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on MAPREDUCE-2817:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12564739/MAPREDUCE-2817.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3236//console

This message is automatically generated.
                
> MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2817
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2817
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.20.2
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Robert Kanter
>            Priority: Minor
>         Attachments: MAPREDUCE-2817.patch, MAPREDUCE-2817.r1.diff
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira