[
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375767#comment-14375767
]
Peter Shi commented on ZOOKEEPER-2139:
--------------------------------------
This is good idea. Some suggestions
1) use Configuration like hdfs's configuration class, can load configuration
from specified locations. So that user can have same experience like hadoop
configuration.
2) remove the jaas.conf, instead, put all jaas.conf information into the
configurations.
3) configuration class have fallback ability, if the required property is not
set in configuration object, it will try to find it in system.properties. Maybe
we can have a boolean flag to control whether to fallback to system properties.
This can keep compatible with previous version's configuration.
> Zookeeper client configuration should not be java system property
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-2139
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
> Affects Versions: 3.5.0
> Reporter: surendra singh lilhore
> Assignee: surendra singh lilhore
>
> I have two ZK client in one JVM, one is secure client and second is normal
> client (For non secure cluster).
> "zookeeper.sasl.client" system property is "true" by default, because of this
> my second client connection is failing.
> We should pass all client configurations in client constructor like HDFS
> client.
> For example :
> {code}
> public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher,
> Configuration conf) throws IOException
> {
> ......
> ......
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
