[jira] [Created] (KAFKA-6417) plugin.path pointing at a plugin directory causes ClassNotFoundException

["Dustin Cote (JIRA)" <ji...@apache.org>]

Dustin Cote created KAFKA-6417:
----------------------------------

             Summary: plugin.path pointing at a plugin directory causes ClassNotFoundException
                 Key: KAFKA-6417
                 URL: https://issues.apache.org/jira/browse/KAFKA-6417
             Project: Kafka
          Issue Type: Bug
          Components: KafkaConnect
    Affects Versions: 1.0.0
            Reporter: Dustin Cote


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

{quote}
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 
{quote}

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. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)