forked from ClickHouse/ClickHouse
-
Notifications
You must be signed in to change notification settings - Fork 8
Alternative syntax for object storage cluster functions #592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Enmk
merged 3 commits into
project-antalya-24.12.2
from
project-antalya-24.12.2-cluster-alt-syntax
Feb 3, 2025
Merged
Alternative syntax for object storage cluster functions #592
Enmk
merged 3 commits into
project-antalya-24.12.2
from
project-antalya-24.12.2-cluster-alt-syntax
Feb 3, 2025
Conversation
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
@ianton-ru, name suggestion: object_storage_cluster, object_storage_max_nodes |
89b24d5
to
dbcffed
Compare
This is an automated comment for commit c88f3d3 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
|
dbcffed
to
c88f3d3
Compare
Merged
ianton-ru
pushed a commit
that referenced
this pull request
May 23, 2025
…-alt-syntax Alternative syntax for object storage cluster functions
ianton-ru
added a commit
that referenced
this pull request
Jul 17, 2025
…-alt-syntax Alternative syntax for object storage cluster functions
13 tasks
ianton-ru
added a commit
that referenced
this pull request
Aug 5, 2025
…-alt-syntax Alternative syntax for object storage cluster functions
13 tasks
13 tasks
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):
Alternative syntax for object storage cluster functions.
Setting
object_storage_max_nodes
to limit used hosts in object storage cluster family functions (s3Cluster, hdfsCluster, etc).Documentation entry for user-facing changes
Alternative syntax for object storage cluster functions. Allows to use simple function name (
s3
,azureBlobStorage
, etc) and call simple or cluster variant depends ofobject_storage_cluster
setting.SELECT * FROM s3(...) SETTINGS object_storage_cluster='cluster'
is equal to
SELECT * FROM s3Cluster('cluster', ...)
Overrided
s3
,azureBlobStorage
,hdfs
,icebergS3
,icebergAzure
,icebergHDFS
,deltaLake
,hudi
table functions.Setting
object_storage_max_nodes
to limit used hosts in object storage cluster family functions (s3Cluster, hdfsCluster, etc).Default value 0 - unlimited.
Sometimes with large clusters makes sense to limit number of hosts involved in distributed request to object storage.
This setting allow to do it.
Now it chooses random hosts from cluster, in common case it should make more or less equable host loading.
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: