[KAFKA-6417] plugin.path pointing at a plugin directory causes ClassNotFoundException

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: connect
• Assignee: Unassigned
• Reporter: Dustin Cote
• Created: 02/Jan/18 18:12
• Updated: 30/Mar/18 15:28

Description

When using the plugin.path configuration for the Connect workers, the user is expected to specify a list containing the following per the docs:

The list should consist of top level directories that include any combination of: a) directories immediately containing jars with plugins and their dependencies b) uber-jars with plugins and their dependencies c) directories immediately containing the package directory structure of classes of plugins and their dependencies

This means we would expect plugin.path=/usr/share/plugins for a structure like /usr/share/plugins/myplugin1,/usr/share/plugins/myplugin2, etc. However if you specify plugin.path=/usr/share/plugins/myplugin1 the resulting behavior is that dependencies for myplugin1 are not properly loaded. This causes a ClassNotFoundException that is not intuitive to debug.

Issue Links

• relates to: KAFKA-6675 Connect workers should log plugin path and available plugins more clearly