Repository navigation
Conversation
Add a database option to choose the transport compression used between the driver and ClickHouse: "lz4" (the default, unchanged) or "none". ClickHouse compresses a query's response on a single thread, which can cap one query's throughput far below what a fast network carries; "none" removes that cap. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Return the result schema of a query without running it, by sending DESCRIBE (<query>) and mapping the columns with the same type mapping as Connection::get_table_schema(). Bound parameters are sent with the DESCRIBE. The schema requests get their own query IDs: the statement's query ID is reused by its data query, and ClickHouse rejects a request whose query ID is still held by an earlier request that is being cleaned up. The settings query starts only after DESCRIBE has finished, because both carry the connection's session ID and ClickHouse rejects overlapping requests on one session. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ClickHouse 26.2 added output_format_arrow_date_as_uint16, default 0, and now writes Date columns as Arrow date32 in ArrowStream. The declared schema still said UInt16, so get_table_schema() and execute_schema() disagreed with the data execute() returns. Read the setting with the other Arrow format settings and map Date to Date32 unless it is 1. Servers without the setting (26.1 and older) always write UInt16, so a missing setting keeps the old mapping. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A connection's requests share one ClickHouse session, and ClickHouse runs one request at a time per session. When a result set is dropped before it is fully read, the server is still finishing that query, so the next query on the same connection failed with SESSION_IS_LOCKED (code 373) every time. The error arrives before any data, so retry execute() and execute_schema() for up to about five seconds (5 ms doubling to 200 ms). A bind given as a stream cannot be replayed, so those requests are not retried. In the new regression test the follow-up query succeeds after 30-40 ms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
A short description of the changes with a link to an open issue.
Checklist
Delete items not relevant to your PR: