[flink] Preserve filesystem configuration in remove_orphan_files
- 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
Filesystem options passed to remove_orphan_files through --conf fs.* can be lost when scope enumeration creates a Fluss connection. The connection reinitializes the filesystem using client configuration, which does not contain these options.
The action should preserve the supplied filesystem configuration throughout initialization and execution.
Map action fs.* options to client.fs.* when creating the connection. Preserve explicit client options and reject conflicting values.
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the remove_orphan_files action and trace the scope-enumeration path where a Fluss connection is created. Follow how action fs.* options and explicit client options enter configuration; done means filesystem settings survive initialization and conflicting values are rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100