You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Phil Zampino (JIRA)" <ji...@apache.org> on 2018/04/30 15:01:00 UTC
[jira] [Commented] (KNOX-1133) Update ZooKeeper URLManager
implementations to use registry client service
[ https://issues.apache.org/jira/browse/KNOX-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458639#comment-16458639 ]
Phil Zampino commented on KNOX-1133:
------------------------------------
I would like to wait until the fix for ZOOKEEPER-2139 is released before addressing this issue.
> Update ZooKeeper URLManager implementations to use registry client service
> ---------------------------------------------------------------------------
>
> Key: KNOX-1133
> URL: https://issues.apache.org/jira/browse/KNOX-1133
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.14.0
> Reporter: Phil Zampino
> Priority: Major
> Fix For: Future
>
>
> There are multiple ZooKeeper-based URLManager implementations:
> * BaseZookeeperURLManager extensions
> ** KafkaZooKeeperURLManager
> ** HBaseZooKeeperURLManager
> ** SOLRZooKeeperURLManager
> * HS2ZooKeeperURLManager
> These should all be updated to support using clients from the remote configuration registry client service.
> Either a single well-known client name can be relied upon by all of these implementations, or there could be a configuration property for each implementation, binding it to a ZooKeeper client.
> Careful consideration should be given to the backward-compatibility requirements around continued support for the current configuration model.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)