Auto-configure Flink Datalake Tiering Service from Fluss cluster instead of manual user specification
- 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/alibaba/fluss/issues) and found nothing similar.
### Motivation
https://github.com/apache/fluss/pull/1426#issuecomment-3138442642
Currently, users must manually set:
```plaintext
--datalake.format paimon
--datalake.paimon.metastore filesystem
--datalake.paimon.warehouse /tmp/paimon
```
These parameters are already configured in `server.yml`.
### Solution
Fetch parameters directly from Fluss cluster, or add validation for user parameter consistency.
### 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 with the server.yml settings and the handling of --datalake.format, --datalake.paimon.metastore, and --datalake.paimon.warehouse. Trace how the Flink Datalake Tiering Service receives these values and compare the alternatives of fetching them from the Fluss cluster or validating user-supplied values. Done means manual configuration is removed or inconsistent parameters are clearly rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100