Expose DialStrategy function to user for custom connection routing #855
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.
Expose a way to have a customized way how connections created: (the result of dial function)
Default
DialStrategy
has following implementationclickhouse.DefaultDialStrategy
:clickhouse.DialStrategy
function receives aclickhouse.Dial
function that needs to be triggered by the user if a new connection is needed. It returns a dedicatedDialResult
that wraps over internal and coupledconnect
struct.It's a hacky solution, as connection and pool management are highly coupled in the library. Until we find a better design in v3, we need to have a trade-off.
Resolves #772