Fluss catalog expose client.security.* to optional options.
- 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.
### Description
A tiny modification to expose client.security.* to optional options. Currently, though we can pass these params using ` helper.validateExcept(CLIENT_SECURITY_PREFIX);` , new modification. it make it visible for catalog management tools to show what option is suggested to use.
### Willingness to contribute
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing helper.validateExcept(CLIENT_SECURITY_PREFIX) and how catalog management tools build their optional options. Confirm which client.security.* parameters are currently accepted, then make sure those options are exposed as suggested values for catalog management; done means the tools visibly include the client.security.* options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100