zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2139) Zookeeper client configuration should not be java system property
Date Sat, 02 May 2015 10:11:06 GMT

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

Rakesh R commented on ZOOKEEPER-2139:

Thanks [~surendrasingh] for pointing out new jar dependency. {{commons-configuration-*.jar}}
will help to hide the complexity of managing the {{config properties}} data structures. But
I'm not very clear about the way of introducing a new jar dependency to the project, existing
users has any concerns with this ? Can we add a new jar at the client side in 3.5 branch?
It would be really great to see the feedback from others.

> 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
>             Fix For: 3.5.2, 3.6.0
>         Attachments: ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch, ZOOKEEPER-2139_2.patch
> 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

View raw message