You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Harsh J (Commented) (JIRA)" <ji...@apache.org> on 2011/12/29 07:26:31 UTC

[jira] [Commented] (HADOOP-3669) Aggregate Framework should allow usage of MultipleOutputFormat

    [ https://issues.apache.org/jira/browse/HADOOP-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177013#comment-13177013 ] 

Harsh J commented on HADOOP-3669:
---------------------------------

Also, MultipleOutputs replaces all other multiple-output mechanisms.
                
> Aggregate Framework should allow usage of MultipleOutputFormat
> --------------------------------------------------------------
>
>                 Key: HADOOP-3669
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3669
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.17.0
>            Reporter: Ankur
>            Assignee: Ankur
>         Attachments: HADOOP-3669_v1.patch
>
>
> Currently the output format is hard-coded to be TextOutputFormat in ValueAggregatorJob responsible for running aggregation jobs using user-defined value aggregator descriptors. This prevents the application writer from specifying an alternate output format.
> A good use case from an application's perspective is to have a sub-type of MultipleOutputFormat set as output format which takes care of redirecting (key, value)
> to different files based on type information encoded in them.
> Applications can extend MultipleTextOutputFormat and define there own multiple output format but they still can't hook it into value aggregator framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira