[jira] Updated: (MAPREDUCE-1979) "Output directory already exists" error in gridmix when gridmix.output.directory is not defined

["Ravi Gummadi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ravi Gummadi updated MAPREDUCE-1979:
------------------------------------

    Attachment: 1979.patch

Attaching patch removing the code that creates the output directory. This creation causes the above reported issue when it is insdie inputDir(as is in the case where gridmix.output.directory is not defined by user and -generate option tries to generate data in inputDir).

> "Output directory already exists" error in gridmix when gridmix.output.directory is not defined
> -----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1979
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1979
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/gridmix
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>         Attachments: 1979.patch
>
>
> "Output directory already exists" error is seen in gridmix when gridmix.output.directory is not defined. When gridmix.output.directory is not defined, then gridmix uses inputDir/gridmix/ as output path for gridmix run. Because gridmix is creating outputPath(in this case, inputDir/gridmix/) at the begining, the output path to generate-data-mapreduce-job(i.e. inputDir) already exists and becomes error from mapreduce.
> There is no need of creating this outputPath in any case(whether user specifies the path using gridmix.output.directory OR gridmix itself considering inputDir/gridmix/ ) because the paths are automatically created for output paths of mapreduce jobs(like mkdir -p).

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