Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
From: ivankelly <git@git.apache.org>
To: dev@zookeeper.apache.org
Reply-To: dev@zookeeper.apache.org
References: <git-pr-227-zookeeper@git.apache.org>
In-Reply-To: <git-pr-227-zookeeper@git.apache.org>
Subject: [GitHub] zookeeper issue #227: ZOOKEEPER-2755 Allow to subclass ClientCnxnSocketNetty...
Content-Type: text/plain
Message-Id: <20170720135928.37C23E04AA@git1-us-west.apache.org>
Date: Thu, 20 Jul 2017 13:59:27 +0000 (UTC)
archived-at: Thu, 20 Jul 2017 13:59:33 -0000

Github user ivankelly commented on the issue:

    https://github.com/apache/zookeeper/pull/227
  
    @eolivelli 
    
    Only the testing usecase appears to hold value for the zookeeper community at large. Your production usecase, is really a production usecase of bookkeeper, and zookeeper is only getting caught up in it because currently bookkeeper has a hard dependency on zookeeper.
    
    As i understand it, you're using bookkeeper locally as a WAL logging library. Even this is not a officially supported usecase for bookkeeper, though it is something the bookkeeper community could explore. In theory it should be straight forward to create something like a local ledger interface that sends all writes to the local disk. But this is the level at which this would hold value for for the larger community.
    
    As such, unfortunately I'm -1 on this patch going in. I'm happy to be overriden by someone with authority on the zk repo though :) (cc: @hanm)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---