[
https://issues.apache.org/jira/browse/KAFKA-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Snehashis Pal updated KAFKA-18211:
----------------------------------
Description:
Connect used to use reflections scanner for scanning and identifying connect
plugins in its plugin.path. This would load said plugins in isolation via the
use of a child first PluginClassloader, which is designed to load class from
its set of URIs before delegating to parent, if not found. This effectively
enforces that if a plugin and its dependencies are part of a plugin path it
would not conflict with other plugins in the plugin path or plugins in
classpath.
GlassGraph was introduced as a replacement for the older reflections scanner in
[KAFKA-15203 Use Classgraph since org.reflections is no longer under
maintainence by PARADOXST · Pull Request #16604 ·
apache/kafka|https://github.com/apache/kafka/pull/16604]. It is used in place
of reflections scanner for finding plugins during plugin scanning. The issue
here is that it is missing any plugins present in isolated plugin paths if its
already present in classpath.
```
```
was:
Connect used to use reflections scanner for scanning and identifying connect
plugins in its plugin.path. This would load said plugins in isolation via the
use of a child first PluginClassloader, which is designed to load class from
its set of URIs before delegating to parent, if not found. This effectively
enforces that if a plugin and its dependencies are part of a plugin path it
would not conflict with other plugins in the plugin path or plugins in
classpath.
GlassGraph was introduced as a replacement for the older reflections scanner in
[KAFKA-15203 Use Classgraph since org.reflections is no longer under
maintainence by PARADOXST · Pull Request #16604 ·
apache/kafka|https://github.com/apache/kafka/pull/16604]. It is used in place
of reflections scanner for finding plugins during plugin scanning. The issue
here is that it is missing any plugins present in isolated plugin paths if its
already present in classpath.
> ClassGraph scanning does not correctly find isolated connect plugins
> --------------------------------------------------------------------
>
> Key: KAFKA-18211
> URL: https://issues.apache.org/jira/browse/KAFKA-18211
> Project: Kafka
> Issue Type: Bug
> Components: connect
> Affects Versions: 4.0.0
> Reporter: Snehashis Pal
> Priority: Blocker
>
> Connect used to use reflections scanner for scanning and identifying connect
> plugins in its plugin.path. This would load said plugins in isolation via the
> use of a child first PluginClassloader, which is designed to load class from
> its set of URIs before delegating to parent, if not found. This effectively
> enforces that if a plugin and its dependencies are part of a plugin path it
> would not conflict with other plugins in the plugin path or plugins in
> classpath.
>
> GlassGraph was introduced as a replacement for the older reflections scanner
> in [KAFKA-15203 Use Classgraph since org.reflections is no longer under
> maintainence by PARADOXST · Pull Request #16604 ·
> apache/kafka|https://github.com/apache/kafka/pull/16604]. It is used in place
> of reflections scanner for finding plugins during plugin scanning. The issue
> here is that it is missing any plugins present in isolated plugin paths if
> its already present in classpath.
>
> ```
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
