hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Gummadi (JIRA)" <j...@apache.org>
Subject [jira] Created: (MAPREDUCE-1979) "Output directory already exists" error in gridmix when gridmix.output.directory is not defined
Date Wed, 28 Jul 2010 11:40:16 GMT
"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


"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.


Mime
View raw message