giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Martella (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-143) Add support for giraph to have a conf file
Date Fri, 10 Feb 2012 00:44:57 GMT

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

Claudio Martella commented on GIRAPH-143:
-----------------------------------------

Yes. I guess this should come along with another ticket for refactoring code to start actually
using the file. We should also bring along our log4j.properties file as well, now that we
have conf/. In general, I'm +1 for this.
                
> Add support for giraph to have a conf file
> ------------------------------------------
>
>                 Key: GIRAPH-143
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-143
>             Project: Giraph
>          Issue Type: New Feature
>          Components: conf and scripts
>    Affects Versions: 0.2.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.2.0
>
>         Attachments: GIRAPH-143.patch
>
>
> Currently one must provide all the Giraph-specific config values either via the command
line or snuck into another project's conf file.  Any self-respecting Hadoop ecosystem project
should have its own conf file.

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

        

Mime
View raw message