[Feature] The multiple partition min-max predicate may lead to regression in partition filter
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Motivation
In https://github.com/apache/paimon/pull/1982 , it introduce the `MultiplePartitionPredicate` to use the min-max to filter partition. It may lead to regression in partition filter.
We can see the manifest file merge in the picture below. If the delete partition contains the latest partition(compaction) and the historical partition(drop partition), it will lead to a wide range scan for the manifest file, due to the min-max filter not works well

### Solution
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing MultiplePartitionPredicate and the manifest-file merge behavior introduced in pull request #1982. Reproduce the case where deleted partitions include both the latest compacted partition and a historical dropped partition, then verify that min-max filtering avoids a wide-range manifest scan without regressing partition filtering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100