Skip to content
Discussion options

You must be logged in to vote

Finally I've reconfigured my clickhouse-clould and switched to native clickhouse connection, instead of http
So far I didn't see such errors anymore.

Also found a note in clickhouse-go driver release notes:

https://github.com/ClickHouse/clickhouse-go/blob/main/CHANGELOG.md

HTTP still has some limitations to be aware of for things like batch flushing and session context, so be cautious when switching over code to this protocol.

@flarco - I suggest put a quote \ reference somewhere in sling docs w.r.t. clickhouse HTTP driver possible issues

Replies: 4 comments 7 replies

Comment options

You must be logged in to vote
3 replies
@flarco
Comment options

@flarco
Comment options

@igrpon
Comment options

Comment options

You must be logged in to vote
1 reply
@igrpon
Comment options

Comment options

You must be logged in to vote
1 reply
@igrpon
Comment options

Comment options

You must be logged in to vote
2 replies
@flarco
Comment options

@igrpon
Comment options

Answer selected by igrpon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants