You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2025/06/12 15:25:00 UTC
[jira] [Created] (KAFKA-19404) Connect's plugin.path documentation does not match behavior
Mickael Maison created KAFKA-19404:
--------------------------------------
Summary: Connect's plugin.path documentation does not match behavior
Key: KAFKA-19404
URL: https://issues.apache.org/jira/browse/KAFKA-19404
Project: Kafka
Issue Type: Task
Components: connect
Reporter: Mickael Maison
The doc currently states:
{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}
In practice plugins are found even if they are in nested directories. For example we can set {{plugin.path}} to {{/var/plugins}} and it will find all these plugins:
{noformat}
/var/plugins
└── nested1
└── nested2
├── plugin1
│ └── plugin1.jar
├── plugin2
│ └── plugin2.jar
├── plugin3
└── plugin3.jar
{noformat}
I think we should adjust the documentation to match the current behavior
--
This message was sent by Atlassian Jira
(v8.20.10#820010)