[
https://issues.apache.org/jira/browse/KAFKA-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419622#comment-16419622
]
Randall Hauch commented on KAFKA-6417:
--------------------------------------
[~ChrisEgerton], have we also thought about logging messages that are a bit
more obvious (for users) as we progress through the different scanning steps?
For example:
{noformat}
Directory '/usr/foo/bar' listed on plugin path, and looking inside for plugin
directories.
Directory '/usr/foo/bar/my-awesome-connector' found under plugin path
`/usr/foo/bar`; looking for connectors, transforms, converters, etc.
Directory '/usr/foo/bar/my-awsomee-connector' found to contain 1 connector and
4 transformations.
{noformat}
Then, per KAFKA-6675, output a summary of what was found and where they were
found. This might help make it obvious when they do something wrong what should
be fixed.
Thoughts?
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)
