SEZ9 commented on issue #10651: URL: https://github.com/apache/seatunnel/issues/10651#issuecomment-5381228962
Thanks for the detailed proposal. Suggest splitting this into independently valuable subtasks: (1) implement `seatunnel.sh --check` (SeaTunnelConfValidateCommand is currently a TODO), (2) export full structured OptionRule metadata per connector, (3) machine-readable validation errors (e.g. JSON with option path, rule violated). Items 1 and 3 are useful even without the AI use case. Could you clarify the intended integration surface for AI: will the metadata export and dry-run validation be exposed as MCP tools/REST endpoints, or only via CLI? This affects the metadata schema design (versioning, JSON schema for OptionRule structures including exclusive/bundled/conditional rules). Recommend converting this discussion into a SIP/design doc on the mailing list or a GitHub Discussion once scope is agreed, then tracking subtasks under an umbrella issue so contributors can pick up individual pieces (metadata export, --check implementation, structured error output). <!-- streview-comment:439 --> -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
