Closed ivankelly closed 5 years ago
@ivankelly When unbinding, should the path for the namespace be deleted from ZooKeeper? Indeed adding zkAclId(null)
solves this problem. I can make a pull request, I'm just confirming if no further changes are required.
@hugomiguelabreu I don't think we need to delete the path. I think adding zkAclId(null)
should fix this problem.
@hugomiguelabreu I don't think we need to delete the path. I think adding
zkAclId(null)
should fix this problem.
I have the PR ready. I have been testing. It seems that, once unbounded a namespace, if the zookeeper path is not deleted, a new binding to the same namespace wont work. Is this the expected outcome?
It seems that, once unbounded a namespace, if the zookeeper path is not deleted, a new binding to the same namespace wont work. Is this the expected outcome?
You probably can't create the binding. but I think you can update the binding.
It seems that, once unbounded a namespace, if the zookeeper path is not deleted, a new binding to the same namespace wont work. Is this the expected outcome?
You probably can't create the binding. but I think you can update the binding.
That's correct, it is possible to update. Thanks.
It looks like the builder for ZooKeeperClient requires something be set for the acl, even if null.