hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Gummadi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1979) "Output directory already exists" error in gridmix when gridmix.output.directory is not defined
Date Thu, 12 Aug 2010 10:53:17 GMT

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

Ravi Gummadi updated MAPREDUCE-1979:

    Attachment: 1979.v1.1.patch

Attaching new patch removing the special check for the default output path existence.
There are many checks that can be done and can be done in a separate JIRA(as they is not relevant
here). Raised MAPREDUCE-2006 to handle these validations.

> "Output directory already exists" error in gridmix when gridmix.output.directory is not
> -----------------------------------------------------------------------------------------------
>                 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, 1979.v1.1.patch, 1979.v1.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.

View raw message