Lake table decouple with Paimon
- 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.
### Description
1. lake table support listPartitions().
2. lake table getTable decouple with paimon
3. FlinkTableFactory createDynamicTableSource decouple with paimon
### 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 the lake table paths for listPartitions() and getTable(), then inspect FlinkTableFactory.createDynamicTableSource() and their Paimon dependencies. Identify the boundaries needed to decouple these components and confirm the affected integration behavior with the existing tests, if present. Done means the requested lake table support remains available without direct Paimon coupling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100