You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/04/09 01:12:13 UTC

[jira] Commented: (ZOOKEEPER-369) remove multiple configs in server/quorums.

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697294#action_12697294 ] 

Patrick Hunt commented on ZOOKEEPER-369:
----------------------------------------

It would be great if we could ping the HBASE team at some point. I seem to remember that they asked for a change in 3.1.1, they are building on config classes in order to do some additional config processing. We should make them aware of this change, both as a heads up for 3.2 but also to get any input they might have -- in particular we should ensure that they can still do what they need to do.

see ZOOKEEPER-279

> remove multiple configs in server/quorums.
> ------------------------------------------
>
>                 Key: ZOOKEEPER-369
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-369
>             Project: Zookeeper
>          Issue Type: Improvement
>    Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1
>            Reporter: Mahadev konar
>             Fix For: 3.2.0
>
>
> currently we have mutliple configs serverconfig and quorumpeerconfig for server and quorums. We can throw away one of these and just keep one of them with some methods returning default values like -1 or null for options that are not available.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.