Skip to content

Implement min/max/null-count partition pruning#67

Merged
gruuya merged 16 commits intomainfrom
min-max-partition-pruning-cu-2vxgc0k
Aug 26, 2022
Merged

Implement min/max/null-count partition pruning#67
gruuya merged 16 commits intomainfrom
min-max-partition-pruning-cu-2vxgc0k

Conversation

@gruuya
Copy link
Contributor

@gruuya gruuya commented Aug 24, 2022

Instead of defaulting to scanning all of the partitions, the goal here is to use the statistical summary for each column in each partition, and based on the filter/qualifier used in the query determine whether some of the partitions are superfluous for getting a correct result. If this determination succeeds simply scope the scan down only to partitions which are relevant to the query.

@gruuya gruuya marked this pull request as ready for review August 24, 2022 12:14
@gruuya gruuya requested a review from mildbyte August 24, 2022 12:15
@gruuya gruuya linked an issue Aug 24, 2022 that may be closed by this pull request
@gruuya gruuya self-assigned this Aug 24, 2022
@gruuya gruuya merged commit 624a14d into main Aug 26, 2022
@gruuya gruuya deleted the min-max-partition-pruning-cu-2vxgc0k branch August 26, 2022 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use the min-max index when planning the query (partition pruning)

2 participants