crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <>
Subject [jira] [Updated] (CRUNCH-132) Add configurable behavior for when a pipeline output directory already exists
Date Thu, 10 Jan 2013 14:02:12 GMT


Josh Wills updated CRUNCH-132:

    Attachment: CRUNCH-132-proto.patch

Hey Dave-- here's what I was working on before the break. I got distracted by the idea of
not forcing a MR job to run before we materialize a collection, which isn't totally germane
to the intent of this JIRA. Let me know if you think any of it is salvageable- I might end
up making it a separate JIRA.
> Add configurable behavior for when a pipeline output directory already exists
> -----------------------------------------------------------------------------
>                 Key: CRUNCH-132
>                 URL:
>             Project: Crunch
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Dave Beech
>            Assignee: Josh Wills
>         Attachments: CRUNCH-132-proto.patch
> Usually when you run a mapreduce job and the output directory already exists, the job
fails (won't start). A Crunch job does run, but results in the output data being duplicated
in the output directory with numbered files that follow on from the previous run. 
> Example
> Run 1, single reducer /output -> /output/part-r-00000
> Run 2, single reducer /output -> /output/part-r-00000, /output/part-r-00001
> I didn't realise I'd run my job twice, so when I looked in the directory it seemed that
there had been 2 reducers and somehow the output had been generated twice, which was confusing.

> I realise this may be by design, but it feels wrong to me. I'd prefer if the behaviour
of a standard mapreduce job was preserved.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message