[
https://issues.apache.org/jira/browse/GIRAPH-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583739#comment-13583739
]
Eli Reisman commented on GIRAPH-524:
------------------------------------
That makes sense, and if this doesn't get changed I won't lose any sleep. I
just think that now that we have Vertex and Edge input formats, it might
confuse people when they see Vertex-named out formats.
I like things like IdWithValueTextOutputFormat, that seems to be exactly what
it is, what it does, and what format the output comes in. The name might lose
information in the manner you are describing, but it also doesn't mislead
anyone regarding its function (i.e. would someone think they need to hunt for
an "EdgeOutputFormat" if they want to see edge weight?)
In the end, if this isn't frustrating or confusing for users, its not a
problem. I think in the user community there is a bit of general frustration
over our IO situation, this particular issue may not really target the source
of that enough to matter? Maybe a quick wiki entry describing our name scheme
and/or the purpose of some of the IO formats is just as good or better.
Thanks for your input, the point is well taken.
> Giraph can receive input from vertex or edge-centric data sets; its output is
> graph data, not "vertices"
> --------------------------------------------------------------------------------------------------------
>
> Key: GIRAPH-524
> URL: https://issues.apache.org/jira/browse/GIRAPH-524
> Project: Giraph
> Issue Type: Bug
> Components: graph
> Reporter: Eli Reisman
> Priority: Minor
> Fix For: 0.2.0
>
>
> It is silly to have any of our Output format names tied to the "vertex" when
> in fact we are just outputting graph data. The output format names should
> reflect the formatting of the output, and perhaps which elements of the graph
> data you want in the output.
> Lets change those names? Then they get shorter too as a bonus.
--
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
