matrixorigin / matrixorigin/matrixone
[Feature Request]: Optimization of Partitioned Table
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 311
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 768
Description
### Is there an existing issue for the same feature request?
- [X] I have checked the existing issues.
### Is your feature request related to a problem?
```Markdown
The current table partitioning acceleration capabilities are not fully satisfactory.
There is a lack of implementation for range and list partition pruning, which limits the potential acceleration benefits.
On the other hand, continuous performance improvements are also needed for existing hash and key partitioned tables.
```
### Describe the feature you'd like
1. Implement partition pruning for **RANGE** and **LIST** partitions to significantly accelerate partitioned tables.
2. Enhance ALTER TABLE syntax to modify partitions with the following options:
- ADD PARTITION (partition_definition) for adding partitions.
- DROP PARTITION partition_names for dropping partitions.
- TRUNCATE PARTITION {partition_names | ALL} for truncating partitions.
3. Performance Acceleration:
- Following a detailed performance analysis of current partitioned tables and addressing any related bug issues, establish a performance baseline for each partitioned table.
- This will help set a benchmark for partition performance improvements in the 1.2 iteration.
- PM will update this issue upon confirmation of the benchmarks.
### Describe implementation you've considered
_No response_
### Documentation, Adoption, Use Case, Migration Strategy
_No response_
### Additional information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.