[
https://issues.apache.org/jira/browse/ZOOKEEPER-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068010#comment-13068010
]
Hadoop QA commented on ZOOKEEPER-781:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12483681/ZOOKEEPER-781.patch
against trunk revision 1148553.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 18 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/401//console
This message is automatically generated.
> provide a generalized "connection strategy" for ZooKeeper clients
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-781
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-781
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client, java client
> Reporter: Patrick Hunt
> Assignee: Qian Ye
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-781.patch, ZOOKEEPER-781.patch,
> ZOOKEEPER-781.patch, ZOOKEEPER-781.patch, ZOOKEEPER-781.patch,
> ZOOKEEPER-781.patch
>
>
> A connection strategy allows control over the way that ZooKeeper clients (we
> would implement this for both c and java apis) connect to a serving ensemble.
> Today we have two strategies, randomized round robin (default) and ordered
> round robin, both of which are hard coded into the client implementation. We
> would generalize this interface and allow users to create their own.
> See this page for more detail:
> http://wiki.apache.org/hadoop/ZooKeeper/ConnectionStrategy
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
