[
https://issues.apache.org/jira/browse/NIFI-16201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107467#comment-18107467
]
ASF subversion and git services commented on NIFI-16201:
--------------------------------------------------------
Commit 0548338cb0ac5f17559b8661d24f73b5c56c1553 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0548338cb0a ]
NIFI-16201: Reload Parameter-driven extra classpath for Connector Methods
(#11574)
* NIFI-16201: Reload Parameter-driven extra classpath for Connector Methods
Stopped components keep a stale InstanceClassLoader after Parameter/asset
classpath changes, so Connector Method discovery and invocation fail with
LinkageError and can hang async verification.
* NIFI-16201: Wrap ClasspathVerifyIT lines that exceeded Checkstyle length
* NIFI-16201: Reload recursive referencers and wrap TypeNotPresentException
Parameter updates can change a Controller Service isolation key, so stopped
referencing components need the same recursive ClassLoader reload as
setProperties(). Connector Method argument resolution can also throw
TypeNotPresentException when a Class annotation member is missing from the
component ClassLoader.
> [Connectors] Support Instance Classloading when invoking Connector Methods
> ---------------------------------------------------------------------------
>
> Key: NIFI-16201
> URL: https://issues.apache.org/jira/browse/NIFI-16201
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bob Paulin
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
> When connector methods are invoked on Components each declared method is
> returned. This works just fine as long as all the classes required for those
> methods are loaded. This is not always the case with components that support
> Instance Classloading. For example a component that rely on classes from a
> JDBC driver that has not yet been loaded.
>
> To support this instance classloading must be invoked with the additional
> classes loaded. This requires similar support to components that verify
> themselves with additional classes. So this functionality must be
> generalized so it can be used on any component not just verifiable ones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
