[KAFKA-16068] Use TestPlugins in ConnectorValidationIntegrationTest to silence plugin scanning errors

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.9.0
• Component/s: connect
• Labels: newbie++
• Assignee: Chris Egerton
• Reporter: Greg Harris
• Created: 29/Dec/23 18:35
• Updated: 20/Aug/24 17:38
• Resolved: 23/Jul/24 17:15

Description

The ConnectorValidationIntegrationTest creates test plugins, some with erroneous behavior. In particular:

 

[2023-12-29 10:28:06,548] ERROR Failed to discover Converter in classpath: Unable to instantiate TestConverterWithPrivateConstructor: Plugin class default constructor must be public (org.apache.kafka.connect.runtime.isolation.ReflectionScanner:138) [2023-12-29 10:28:06,550]
ERROR Failed to discover Converter in classpath: Unable to instantiate TestConverterWithConstructorThatThrowsException: Failed to invoke plugin constructor (org.apache.kafka.connect.runtime.isolation.ReflectionScanner:138)
java.lang.reflect.InvocationTargetException

These plugins should be eliminated from the classpath, so that the errors do not appear in unrelated tests. Instead, plugins with erroneous behavior should only be present in the TestPlugins, so that tests can opt-in to loading them.

There are already plugins with private constructors and throwing-exceptions-constructors, so they should be able to be re-used.

 

Issue Links

• is caused by: KAFKA-13328 Connect does not perform preflight validation for per-connector header converters
• is caused by: KAFKA-13329 Connect does not perform preflight validation for per-connector key and value converters
• links to: GitHub Pull Request #15642
• links to: GitHub Pull Request #16647