[server] Push partition filtering to the server-side to reduce network bandwidth usage
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 119
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/alibaba/fluss/issues) and found nothing similar.
### Motivation
Push partition filtering to the server-side to reduce network bandwidth usage
we can optimize on the ZK side: when the ResolvedPartitionSpec is a complete partition spec, we can directly retrieve the partition instead of scanning all partitions. This can satisfy some scenarios.
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing ResolvedPartitionSpec through the server-side partition lookup and ZK-related code paths. Confirm how complete partition specifications are currently handled, then determine the tests or measurements needed to show that direct retrieval reduces scanning and network usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100