Propagate Native format settings properly for client-server communication#73924
Merged
Avogar merged 5 commits intoClickHouse:masterfrom Feb 5, 2025
Merged
Propagate Native format settings properly for client-server communication#73924Avogar merged 5 commits intoClickHouse:masterfrom
Avogar merged 5 commits intoClickHouse:masterfrom
Conversation
Contributor
|
This is an automated comment for commit f0a1036 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
Member
|
from tests - apparently there is some interference with JSON format... |
1 task
Member
Author
|
It's because of setting |
yakov-olkhovskiy
approved these changes
Jan 14, 2025
1 task
Merged
via the queue into
ClickHouse:master
with commit Feb 5, 2025
b2f6e13
112 of 115 checks passed
This was referenced Feb 5, 2025
robot-ch-test-poll2
added a commit
that referenced
this pull request
Feb 5, 2025
Cherry pick #73924 to 24.12: Propagate Native format settings properly for client-server communication
robot-clickhouse
added a commit
that referenced
this pull request
Feb 5, 2025
…or client-server communication
robot-ch-test-poll2
added a commit
that referenced
this pull request
Feb 5, 2025
Cherry pick #73924 to 25.1: Propagate Native format settings properly for client-server communication
robot-clickhouse
added a commit
that referenced
this pull request
Feb 5, 2025
…r client-server communication
robot-clickhouse-ci-2
added a commit
that referenced
this pull request
Feb 5, 2025
Backport #73924 to 25.1: Propagate Native format settings properly for client-server communication
Avogar
added a commit
that referenced
this pull request
Feb 10, 2025
Backport #73924 to 24.12: Propagate Native format settings properly for client-server communication
robot-ch-test-poll3
added a commit
that referenced
this pull request
Feb 10, 2025
Cherry pick #73924 to 24.8: Propagate Native format settings properly for client-server communication
robot-clickhouse
added a commit
that referenced
this pull request
Feb 10, 2025
…r client-server communication
robot-ch-test-poll3
added a commit
that referenced
this pull request
Feb 10, 2025
Cherry pick #73924 to 24.11: Propagate Native format settings properly for client-server communication
robot-clickhouse
added a commit
that referenced
this pull request
Feb 10, 2025
…or client-server communication
robot-clickhouse-ci-1
added a commit
that referenced
this pull request
Feb 10, 2025
Backport #73924 to 24.11: Propagate Native format settings properly for client-server communication
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Propogate Native format settings properly for client-server communication.
Closes #73883
Documentation entry for user-facing changes
CI Settings (Only check the boxes if you know what you are doing)
All builds in Builds_1 and Builds_2 stages are always mandatory
and will run independently of the checks below: