You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Enrico Olivelli (JIRA)" <ji...@apache.org> on 2019/06/07 12:14:00 UTC

[jira] [Resolved] (ZOOKEEPER-3416) Remove redundant ServerCnxnFactoryAccessor

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enrico Olivelli resolved ZOOKEEPER-3416.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.6.0

Issue resolved by pull request 969
[https://github.com/apache/zookeeper/pull/969]

> Remove redundant ServerCnxnFactoryAccessor
> ------------------------------------------
>
>                 Key: ZOOKEEPER-3416
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3416
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: tests
>    Affects Versions: 3.6.0
>            Reporter: Michael Han
>            Assignee: Michael Han
>            Priority: Minor
>              Labels: Twitter, pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> We have two ways to access the private zkServer inside ServerCnxnFactory, and there is really no need to keep maintaining both. We could remove ServerCnxnFactoryAccessor when we added the public accessor for ServerCnxnFactory in ZOOKEEPER-1346, but we did not.
> The solution is to consolidate all access of the zkServer through the public accessor of ServerCnxnFactory. The end result is cleaner code base and less confusion.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)