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

jirapos...@reviews.apache.org commented on GIRAPH-64:
-----------------------------------------------------



bq.  On 2011-11-03 05:32:49, Jake Mannix wrote:
bq.  > It would be super cool if, like in Mahout and Hadoop, we could print out 
the set of Vertex impls / algorithms / actions available.  In Mahout, we have a 
properties file which we keep updating.  Even nicer (maybe?) would be to just 
search the classpath for all classes which implement BasicVertex, and list 
them.  Even cooler: have a new abstract method on BasicVertex "String 
getHelp()" which GiraphRunner could run via reflection to get the help output 
for the task.
bq.  
bq.  Jakob Homan wrote:
bq.      Absolutely. Another JIRA?

abstract method or annotation? 

Nice thing about annotations is that you can hook into them during compilation 
and produce docs...


- Dmitriy


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2700/#review3023
-----------------------------------------------------------


On 2011-11-12 02:03:20, Jakob Homan wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/2700/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2011-11-12 02:03:20)
bq.  
bq.  
bq.  Review request for giraph.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  create giraphrunner
bq.  
bq.  
bq.  This addresses bug GIRAPH-64.
bq.      https://issues.apache.org/jira/browse/GIRAPH-64
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    /trunk/bin/giraph PRE-CREATION 
bq.    /trunk/pom.xml 1196926 
bq.    /trunk/src/main/assembly/assembly.xml PRE-CREATION 
bq.    /trunk/src/main/java/org/apache/giraph/GiraphRunner.java PRE-CREATION 
bq.    /trunk/src/main/java/org/apache/giraph/graph/GraphMapper.java 1196926 
bq.  
bq.  Diff: https://reviews.apache.org/r/2700/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Jakob
bq.  
bq.


                
> 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
>            Assignee: Jakob Homan
>         Attachments: GIRAPH-64-2.patch, GIRAPH-64.patch
>
>
> 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

        

Reply via email to