[spark] Partition filter pushdown for lake-enabled tables
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Description
Follow-up to #3240, which explicitly carved out lake-enabled tables.
Mirror the existing FlussUpsertScan / FlussAppendScan plumbing - thread partitionPredicate through the scan builder, the scan, and the batch.
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the existing FlussUpsertScan and FlussAppendScan plumbing, then trace how the scan builder, scan, and batch pass predicates. Thread partitionPredicate through the corresponding lake-enabled table path and verify that partition filters are pushed down there as they are for the existing scan paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100