For me, it depends on how people like to run Giraph, and these tool in general. I have always felt like the advantage of GIraphRunner and bin/giraph are that it gets people in the frame of mind to re-use existing IO formats at the command line if they can, which (especially as we get more of them, and improve the ones we have) is IMHO a really good idea, especially to simplify the "test drive" for new users and evaluators in need of a graph processing solution.
For me, any configuration setting that is globally important to how Giraph runs, and is not best tuned for all algorithms or clusters at a default setting is a great candidate for a command line option of its own. On Wed, Jan 16, 2013 at 4:02 PM, Claudio Martella (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/GIRAPH-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555635#comment-13555635] > > Claudio Martella commented on GIRAPH-431: > ----------------------------------------- > > +1. > > i was guessing few days ago if we should also expose the number of compute > threads and OOC stuff via explicit options in GiraphRunner, or keep it via > -ca. > > Opinions? > > > Support edge and vertex value input formats in GiraphRunner > > ----------------------------------------------------------- > > > > Key: GIRAPH-431 > > URL: https://issues.apache.org/jira/browse/GIRAPH-431 > > Project: Giraph > > Issue Type: Improvement > > Reporter: Alessandro Presta > > Assignee: Alessandro Presta > > Attachments: GIRAPH-431.patch > > > > > > In GiraphRunner, should be possible to specify both a VertexInputFormat > and an EdgeInputFormat or just one of the two. > > -- > 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 >
