[ 
https://issues.apache.org/jira/browse/NIFI-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482605#comment-17482605
 ] 

ASF subversion and git services commented on NIFI-9576:
-------------------------------------------------------

Commit 16174060411a7943c21d60cd2916ec4b3c682d90 in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1617406 ]

NIFI-9576: Introduced a BlockListClassLoader that can be used by stateless in 
order to isolate both the Stateless Engine and the NiFi extensions from 
extraneous classes that exist in the System ClassLoader

This closes #5705.

Signed-off-by: Peter Turcsanyi <[email protected]>


> ClassLoader isolation for Stateless NiFi
> ----------------------------------------
>
>                 Key: NIFI-9576
>                 URL: https://issues.apache.org/jira/browse/NIFI-9576
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: NiFi Stateless
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When Stateless NiFi is running embedded within an application (like Kafka 
> Connect), then the hosting app has its own class loader mechanism and system 
> class path that may conflict with NiFi's class loading / class path. E.g. 
> Kafka's {{libs}} folder (v2.8.x) contains {{jackson}} dependencies that are 
> incompatible with NiFi (v1.15.x).
> Implement a class loading mechanism that is able to isolate NiFi's class 
> loaders from the embedding environment.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to