Skip to content
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

Feature: Table Cluster Key #4268

Closed
BohuTANG opened this issue Feb 27, 2022 · 1 comment
Closed

Feature: Table Cluster Key #4268

BohuTANG opened this issue Feb 27, 2022 · 1 comment
Assignees
Labels
A-storage Area: databend storage C-feature Category: feature
Milestone

Comments

@BohuTANG
Copy link
Member

BohuTANG commented Feb 27, 2022

Summary

Goals for reduce the partition scans.
In Fuse engine, physical data will be stored follow the append order, if one column data is scattered across multiple partitions, the query related to this column will be bad.

ALTER TABLE t1 CLUSTER BY (column1, column2)
When the table is re-clustered, new partitions will be created and the physical data will re-partition by column1 and column2.

This is same as snowflake did.

Reference:
https://docs.snowflake.com/en/user-guide/tables-clustering-keys.html
https://docs.snowflake.com/en/user-guide/tables-clustering-micropartitions.html#label-data-clustering
https://docs.snowflake.com/en/sql-reference/functions/system_clustering_information.html

@BohuTANG BohuTANG added C-feature Category: feature A-storage Area: databend storage labels Feb 27, 2022
@BohuTANG BohuTANG mentioned this issue Feb 27, 2022
4 tasks
@zhyass zhyass self-assigned this Mar 1, 2022
@zhyass
Copy link
Member

zhyass commented Apr 19, 2022

#4946

@Xuanwo Xuanwo added this to the v0.8 milestone May 20, 2022
@Xuanwo Xuanwo added A-storage Area: databend storage and removed A-storage Area: databend storage labels May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-storage Area: databend storage C-feature Category: feature
Projects
Archived in project
Development

No branches or pull requests

3 participants