[
https://issues.apache.org/jira/browse/NIFI-14546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950111#comment-17950111
]
David Handermann commented on NIFI-14546:
-----------------------------------------
[~turcsanyip] the StandardExtensionDiscoveringManager specifically checks for
and removes service references from parent Class Loaders, so it sounds like
that should also be evaluated to determine why it is not filtering out the
reference as expected.
That being said, there is probably value in adjusting the module structure to
avoid this regardless.
> nifi-kafka-service-aws duplicates Kafka3ConnectionService
> -----------------------------------------------------------
>
> Key: NIFI-14546
> URL: https://issues.apache.org/jira/browse/NIFI-14546
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Peter Turcsanyi
> Priority: Major
> Attachments: Kafka3ConnectionService_duplicated.png
>
>
> The recently added nifi-kafka-service-aws module (NIFI-12952) depends on
> [nifi-kafka-3-service|https://github.com/apache/nifi/blob/32b9a99a808245f18adde97af4cae017103a1838/nifi-extension-bundles/nifi-kafka-bundle/nifi-kafka-service-aws/pom.xml#L35-L40]
> and the service jar is bundled in the aws service nar (in addition to its
> own nar). As a result, Kafka3ConnectionService became duplicated as the
> service loader deploys the component from 2 different bundles.
> The common code needs to be extracted into a regular (non-component) shared
> module and both service modules should depend on that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
