Mailing-List: contact crunch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: crunch-dev@incubator.apache.org
Date: Fri, 28 Sep 2012 10:57:07 +1100 (NCT)
From: "Robert Chu (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <1027776147.136883.1348790227880.JavaMail.jiratomcat@arcas>
In-Reply-To: <1087572468.136875.1348789867441.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CRUNCH-82) Support OutputFormats not based on
 FileOutputFormat when writing to multiple targets.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Chu updated CRUNCH-82:
-----------------------------

    Attachment: multipleoutputs.patch

Here's a fix for some of these issues. Targets that use non HDFS based OutputFormats will still have to call:

FileOutputFormat.setOutputPath

in their configureForMapReduce method since job submission uses TextOutputFormat when no OutputFormat is set for a job (because writing to multiple targets uses the MultipleOutputs library). Job submission then validates the outputPath set in the job's configuration which will fail unless the above method is called.
                
> Support OutputFormats not based on FileOutputFormat when writing to multiple targets.
> -------------------------------------------------------------------------------------
>
>                 Key: CRUNCH-82
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-82
>             Project: Crunch
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Robert Chu
>         Attachments: multipleoutputs.patch
>
>
> Currently, writing to multiple targets with OutputFormats that aren't subclasses of FileOutputFormat fails because Crunch expects these targets to write to hdfs.

--
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: http://www.atlassian.com/software/jira