[
https://issues.apache.org/jira/browse/HADOOP-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611420#action_12611420
]
Hadoop QA commented on HADOOP-3669:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12385387/HADOOP-3669_v1.patch
against trunk revision 674671.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2806/console
This message is automatically generated.
> Aggregate Framework should allow usage of MultipleOutputFormat
> --------------------------------------------------------------
>
> Key: HADOOP-3669
> URL: https://issues.apache.org/jira/browse/HADOOP-3669
> Project: Hadoop Core
> 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.
-
You can reply to this email to add a comment to the issue online.
