liunaijie opened a new issue, #8576: URL: https://github.com/apache/seatunnel/issues/8576
### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### Describe the proposal This issue has two proposal: 1. move all parameter that user can adjust to a single class, connector use `XXXSourceConfig/ XXXSourceOptions`. Update `EnvCommandOptions` to describe the parameters we can adjust in `Env` config. Update `ServerConfigOptions` to describe the parameters we can adjust about `Zeta Engine` config. The benefits: - We can easily know what parameter can be adjusted, that can help us to tune the performance. - When version release, we can easily know which parameter has been changed, which can break the user version upgrade, which is added in new version, So we can record this into version upgrade document (although we don't have it yet). 2. refactor connector, implement `TableSourceFactory`, `TableSinkFactory` interface and implement `createSource`, `createSink`, `optionRule` method. In `optionRule` method, describe which parameter is necessary, which is optional, which are the conflicts with other parameter. (need action1 done) Move the connector creation logic from `Connector` to `ConnectorFactory`. The benefits: - Know the relationship between parameters. Use the `optionRule` check the config before create connector instance. - This can be used in SeaTunnelWeb. Welcome to do this with me, I will list the task later. ### Task list I will list the task later. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@seatunnel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
