You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Connecting to the DB with DNS SRV records is a fairly common approach when you need some load balancing. E.g. MySQL and MongoDB support it. It would be great that the clickhouse-go can support connecting to the server by DNS SRV records.
Describe the solution you'd like
The clickhouse-go can support connecting to the server by DNS SRV records.
It can be set in the DSN with a unique protocol clickhouse+srv://:
typeOptionsstruct {
// Other optionsResolveSRVbool// Resolve the DNS SRV records and populate the list of hosts to connect to
}
Describe alternatives you've considered
It is possible to resolve the DNS SRV records outside the driver, and provide the resolved host list to the driver when opening a conn. However, the SRV records need to be continuously resolved as the host list could change. One alternative is that we resolve the DNS and create a new conn every time we interact with the DB, but it feels wasteful and slow.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Connecting to the DB with DNS SRV records is a fairly common approach when you need some load balancing. E.g. MySQL and MongoDB support it. It would be great that the clickhouse-go can support connecting to the server by DNS SRV records.
Describe the solution you'd like
The clickhouse-go can support connecting to the server by DNS SRV records.
It can be set in the DSN with a unique protocol
clickhouse+srv://
:Or controlled by a flag in Options:
Describe alternatives you've considered
It is possible to resolve the DNS SRV records outside the driver, and provide the resolved host list to the driver when opening a conn. However, the SRV records need to be continuously resolved as the host list could change. One alternative is that we resolve the DNS and create a new conn every time we interact with the DB, but it feels wasteful and slow.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: