You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Turcsanyi (Jira)" <ji...@apache.org> on 2022/01/26 16:32:00 UTC

[jira] [Resolved] (NIFI-9576) ClassLoader isolation for Stateless NiFi

     [ https://issues.apache.org/jira/browse/NIFI-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Turcsanyi resolved NIFI-9576.
-----------------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed

> 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: Mark Payne
>            Priority: Major
>             Fix For: 1.16.0
>
>          Time Spent: 0.5h
>  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)