[
https://issues.apache.org/jira/browse/KAFKA-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416438#comment-16416438
]
Chris Egerton edited comment on KAFKA-6417 at 3/28/18 12:14 AM:
----------------------------------------------------------------
[~cotedm] Alright, given that insight I agree that issuing warnings for unused
JARs would just end up flooding logs with often-unnecessary messages and a
different approach is warranted.
To clarify, do you think it'd make more sense at this point to pursue changing
the plugin structure or to catch the {{ClassNotFoundException}} caused by
improper structure and add an error message about said improper structure
before failing the connector? Open to either at this point, although still
leaning away from changing plugin structure a small amount.
was (Author: chrisegerton):
Alright, given that insight I agree that issuing warnings for unused JARs would
just end up flooding logs with often-unnecessary messages.
To clarify, do you think it'd make more sense at this point to pursue changing
the plugin structure or to catch the {{ClassNotFoundException}} caused by
improper structure and add an error message about said improper structure
before failing the connector? Open to either at this point, although still
leaning away from changing plugin structure a small amount.
> 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)
