[
https://issues.apache.org/jira/browse/KNOX-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Zampino updated KNOX-1133:
-------------------------------
Description:
There are multiple ZooKeeper-based URLManager implementations:
* BaseZookeeperURLManager extensions
** KafkaZooKeeperURLManager
** HBaseZooKeeperURLManager
** SOLRZooKeeperURLManager
* HS2ZooKeeperURLManager
These should all be updated to employ 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.
was:
There are multiple ZooKeeper-based URLManager implementations:
* BaseZookeeperURLManager extensions
** KafkaZooKeeperURLManager
** HBaseZooKeeperURLManager
** SOLRZooKeeperURLManager
* HS2ZooKeeperURLManager
These should all be updated to employ clients from the remote configuration
registry client service.
Careful consideration should be given to the backward-compatibility
requirements around continued support for the current configuration model.
> 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: Bug
> Components: Server
> Affects Versions: 0.14.0
> Reporter: Phil Zampino
> Fix For: 0.15.0
>
>
> There are multiple ZooKeeper-based URLManager implementations:
> * BaseZookeeperURLManager extensions
> ** KafkaZooKeeperURLManager
> ** HBaseZooKeeperURLManager
> ** SOLRZooKeeperURLManager
> * HS2ZooKeeperURLManager
> These should all be updated to employ 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
(v6.4.14#64029)
