ZOOKEEPER-4966: Decouple ZKConfig from QuorumPeerConfig.ConfigException
#2306
+52
−46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ZKConfigis client accessible, it should avoid accessing server sideQuorumPeerConfig.Changes:
org.apache.zookeeper.common.ConfigExceptionforZKConfig(String configPath).QuorumPeerConfig.ConfigExceptiona subclass of above.QuorumPeerConfig.ConfigExceptionif possible.Given above changes, this pr maintain abi compatibility with old releases.
Breaking change:
ZKConfig(String configPath)throwsorg.apache.zookeeper.common.ConfigExceptionnow but notQuorumPeerConfig.ConfigException, so developers have to fix it to compile.This is a small step towards ZOOKEEPER-233.
Refs: ZOOKEEPER-233, ZOOKEEPER-835, and ZOOKEEPER-842.