[
https://issues.apache.org/jira/browse/ZOOKEEPER-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706102#action_12706102
]
Benjamin Reed commented on ZOOKEEPER-390:
-----------------------------------------
I propose that the zookeeper URL has the following forms:
zk://host:port,host:port,.../path
and
zk:URL!/path
so if you construct a ZooKeeper object with
zk://h1:2181,h2:2181,h3:2181/apps/myapp would create a ZooKeeper object pointed
at the cluster made up of h1, h2, and h3 rooted at /apps/myapp. for backwards
compatibility if we construct with h1:2181,h2:2181,h3:2181, it will be
equivalent to zk://h1:2181,h2:2181,h3:2181/.
if the list of hosts that make up the service are stored in the url
http://abc.com/zkServers.txt, zk:http://abc.com/zkServers.txt!/ would be used
to construct a ZooKeeper object.
> zookeeper url scheme
> --------------------
>
> Key: ZOOKEEPER-390
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-390
> Project: Zookeeper
> Issue Type: Improvement
> Reporter: Benjamin Reed
>
> we need a URL scheme for zookeeper. i think such a scheme could encode
> various forms of server lists as well as chroot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
