[
https://issues.apache.org/jira/browse/GIRAPH-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379892#comment-14379892
]
Sergey Edunov commented on GIRAPH-1000:
---------------------------------------
That would be a great addition to Giraph!
I was thinking about it a while ago. Seems like we can implement it in a
similar to multiple input format way. See for example:
org.apache.giraph.io.formats.multi.MultiVertexInputFormat and other classes in
the same package. This is essentially a wrapper around a list on inputs
providing the same API as single input format does.
In a same way we can have a wrapper around VertexOutputFormat and
EdgeOutputFormat providing same APIs, and then just plug them in.
We also need this feature, so I'll be happy to help
> Multi Output support
> --------------------
>
> Key: GIRAPH-1000
> URL: https://issues.apache.org/jira/browse/GIRAPH-1000
> Project: Giraph
> Issue Type: Improvement
> Components: bsp, conf and scripts, graph
> Affects Versions: 1.0.0, 1.1.0, 1.2.0-SNAPSHOT
> Reporter: Alessio Arleo
> Labels: features
>
> Hadoop natively supports multiple outputs. The objective is to extend Giraph
> to support multiple output formats during a single giraph run.
> According to the official Hadoop apidocs*, to take advantage of multiple
> outputs the the pattern is the following:
> - Modify the job submission
> - Modify the reducer class to write on the declared different outputs
> Since Giraph jobs are executed as mappers, probably this approach (or at
> least its second part) is not feasible, so further investigation is necessary.
> *https://hadoop.apache.org/docs/r1.2.1/api/org/apache/hadoop/mapreduce/lib/output/MultipleOutputs.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
