[
https://issues.apache.org/jira/browse/KNOX-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426645#comment-17426645
]
Larry McCay commented on KNOX-1852:
-----------------------------------
Due to upcoming release of 1.6.0 and the need for an incompatible change coming
up for log4j migration, we are moving this out to the 2.0.0 release. As of now,
1.6.0 will be the last 1.x.x release due to the incompatible change. If there
is a critical need for this in 1.6.0 please feel free to move the fixVersion
back to 1.6.0 with a note of justification.
> Simplify ZookeeperRemoteAliasService and make it generic
> --------------------------------------------------------
>
> Key: KNOX-1852
> URL: https://issues.apache.org/jira/browse/KNOX-1852
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Sandeep More
> Priority: Major
> Fix For: 2.0.0
>
>
> ZookeeperRemoteAliasService class can be made more generic to support future
> implementations of AliasService that depend on
> RemoteConfigurationRegistryClient class. Currently, we only have Zookeeper
> implementation. The purpose of this Jira is to document the following two
> enhancements to ZookeeperRemoteAliasService class to make it more generic:
> # Change the name to something more generic
> # Move the Zookeeper specific implementation to the class that implements
> RemoteConfigurationRegistryClient, CuratorClientService in case of Zookeeper
> service. As an example.
> ## ZookeeperRemoteAliasService.{color:#ffc66d}ensureEntry{color}() logic
> ## {color:#9876aa}AUTHENTICATED_USERS_ALL{color}
> ## {color:#9876aa}TYPE{color}
> This will be helpful when we decide to implement support for services like
> consul.
> This is a result of offline discussion with [[email protected]] about
> KNOX-1851.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)