I think this specific behavior irritates a lot of new users. We may as well provide a Generic Option to overwrite the output directory if set. That way, we at least help avoid typing a whole delete command. If you agree, please file an improvement request against MAPREDUCE project on the ASF JIRA.
On Thu, Aug 23, 2012 at 6:58 PM, Bertrand Dechoux <[email protected]> wrote: > I don't think so. The client is responsible for deleting the resource > before, if it might exist. > Correct me if I am wrong. > > Higher solution (such as Cascading) usually provides a way to define a > strategy to handle it : KEEP, REPLACE, UPDATE ... > http://docs.cascading.org/cascading/2.0/javadoc/cascading/tap/SinkMode.html > > Regards > > Bertrand > > On Thu, Aug 23, 2012 at 3:15 PM, Daniel Hoffman > <[email protected]>wrote: > >> With respect to the FileAlreadyExistsException which occurrs when a >> duplicate directory is discovered by an OutputFormat, >> Is there a hadoop property that is accessible by the client to disable >> this behavior? >> >> IE, disable.file.already.exists.behaviour=true >> >> Thank You >> Daniel G. Hoffman >> > > > > -- > Bertrand Dechoux -- Harsh J
