[
https://issues.apache.org/jira/browse/NIFI-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13795:
------------------------------------
Fix Version/s: 2.0.0-M5
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Uploaded NAR can select incorrect parent NAR
> --------------------------------------------
>
> Key: NIFI-13795
> URL: https://issues.apache.org/jira/browse/NIFI-13795
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 2.0.0-M4
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are two scenarios where an uploaded NAR can select an undesirable
> parent NAR.
> 1. During Upload
> If the user is planning to uploads a service-api-nar, service-impl-nar, and
> processor-nar, where there also exists other versions of these same NARs
> provided by NiFi, the NARs must be uploaded in the correct order (API first,
> followed by impls).
> Otherwise if the processor-nar, or service-impl-nar, is uploaded first, they
> will select the existing compatible API NAR as the parent, and when the other
> API NAR is uploaded, nothing will be using it.
> 2. During Restart
> Similarly, during restart, the NAR Manager gets a listing of all the NAR
> files known the NAR manager from listing the contents of the persistence
> directory, and then passes all of these files to be loaded to NarLoader.
> If the same above three NARs are in the list, and the processor-nar or
> service-impl-nar is loaded before the API NAR, they will select the existing
> compatible API NAR, instead of the API NAR from the NAR Manager.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)