[
https://issues.apache.org/jira/browse/GIRAPH-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136704#comment-13136704
]
Owen O'Malley commented on GIRAPH-64:
-------------------------------------
I guess I should expand on that a bit. So the standard giraph main should build
up the job and submit it and just provide a cli option to override the vertex
and automatically put both the giraph.jar and my-awesome.jar into the dist
cache.
> Create VertexRunner to make it easier to run users' computations
> ----------------------------------------------------------------
>
> Key: GIRAPH-64
> URL: https://issues.apache.org/jira/browse/GIRAPH-64
> Project: Giraph
> Issue Type: New Feature
> Reporter: Jakob Homan
>
> Currently, if a user wants to implement a Giraph algorithm by extending
> {{Vertex}} they must also write all the boilerplate around the {{Tool}}
> interface and bundle it with the Giraph jar (or get Giraph on the classpath
> and playing nice with the implementation). For example, what is included in
> the PageRankBenchmark and what Kohei has done:
> https://github.com/smly/java-Giraph-LabelPropagation It would be better if
> we had perhaps a Vertex implementation to be subclassed that already had all
> the standard Tooling included such that all one had to run would be (assuming
> the Giraph jar was already on the classpath):
> {noformat}hadoop jar my-awesome-vertex.jar my.awesome.vertex -i jazz_input -o
> jazz_output -if org.apache.giraph.lib.in.text.adjacency-list.LongDoubleDouble
> -of org.apache.giraph.lib.out.text.adjacency-list.LongDoubleDouble{noformat}
> This wouldn't work with every algorithm, but would be useful in a large
> number of cases.
--
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
