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/cascad
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.
Well, I'm using the MultipleOutputs capability to create a directory
Structure with Dates.
So I'm managing this myself.
What I've found, and I could be doing this wrong... is that I still have to
tell the Tool that I want to use a:
TextOutputFormat or a FileOutputFormat, and then, have to tell the
Daniel,
Perhaps you want your OutputFormat set as NullOutputFormat. That does
not carry any checks for output directory pre-existence.
On Thu, Aug 23, 2012 at 9:47 PM, Daniel Hoffman
wrote:
> Well, I'm using the MultipleOutputs capability to create a directory
> Structure with Dates.
> So I'm ma
