Expose X-ClickHouse-Server-Display-Name header via client-v2 API#2744
Merged
chernser merged 2 commits intoClickHouse:mainfrom Feb 14, 2026
Merged
Conversation
Extract the server display name from HTTP response headers and surface it through OperationMetrics, QueryResponse, InsertResponse, and CommandResponse, following the existing queryId pattern. Signed-off-by: Itamar Syn-Hershko <itamar@bigdataboutique.com>
chernser
reviewed
Feb 13, 2026
chernser
requested changes
Feb 13, 2026
Contributor
|
Good day, @synhershko ! Thanks! |
Contributor
Author
|
@chernser updated |
chernser
approved these changes
Feb 14, 2026
Contributor
|
Thank you @synhershko ! |
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.
Extract the server display name from HTTP response headers and surface it through OperationMetrics, QueryResponse, InsertResponse, and CommandResponse, following the existing queryId pattern.
Note
Low Risk
Additive API surface that only reads and exposes a small, whitelisted set of response headers; minimal impact on request/response flow aside from extra header collection.
Overview
Client-v2 now captures a whitelisted set of ClickHouse HTTP response headers and attaches them to operation results.
Clientpasses collected headers intoQueryResponseandInsertResponse, whileQueryResponse,InsertResponse, andCommandResponseexposegetServerDisplayName()(fromX-ClickHouse-Server-Display-Name) plusgetResponseHeaders()for the full collected map.HttpAPIClientHelperaddscollectResponseHeaders()with a fixed whitelist to avoid exposing arbitrary headers.Written by Cursor Bugbot for commit 8932875. This will update automatically on new commits. Configure here.