C0urante opened a new pull request, #14304: URL: https://github.com/apache/kafka/pull/14304
[Jira 1](https://issues.apache.org/jira/browse/KAFKA-13328), [Jira 2](https://issues.apache.org/jira/browse/KAFKA-13329) Adds preflight validation checks for key, value, and header converter classes specified in connector configurations. For each converter type, these checks verify that: - The class has a public, no-args constructor - The class can be instantiated without an exception being thrown - The class is not abstract - - In this case, a list of possible child classes is provided in a user-friendly error message - The class implements the expected interface There are two components to the linked Jira tickets: this validation (which is fairly straightforward), and more sophisticated logic that leverages `ConfigDef` objects provided by these plugin classes. For ease of review, I'm planning on filing two PRs for these tickets, but instead of grouping by ticket (which would include all key/value converter changes in one ticket and all header converter changes in another), I think it might be easier to group by the kind of validation we're performing. If that's acceptable, the next PR will add `ConfigDef`-based validation for key, value, and header converters. ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status - [ ] Verify documentation (including upgrade notes) -- 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]
