giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-623) Website Documentation: table of parameters
Date Thu, 20 Jun 2013 17:46:20 GMT

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

Nitay Joffe commented on GIRAPH-623:
------------------------------------

Where is the latest patch? All I see is the python version in the one you uploaded. In general
I would vote for the Java option as it is more tied to the code and therefore will not break
anytime one of the *Option APIs changes. Our jars should already have manifests. You mean
you want to make this the main class that is launched if you don't specify a class? I would
vote against that, it doesn't make sense to me that this be the default thing that gets run.
However you can easily run this by just doing java -cp <jar> <class> as you mentioned,
so I think that's good enough.
                
> Website Documentation: table of parameters
> ------------------------------------------
>
>                 Key: GIRAPH-623
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-623
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Claudio Martella
>         Attachments: GIRAPH-623.patch
>
>
> Would be nice to have a table with all the parameters in GiraphConstants, with defaults
and relative javadoc explanation.

--
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

Mime
View raw message