[MINIFI-408] Improve handling of bundle versioning in NARs with other NARs as dependencies

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.2.0
• Fix Version/s: 0.3.0
• Component/s: Core Framework
• Assignee: Aldrin Piri
• Reporter: Aldrin Piri
• Created: 26/Oct/17 13:10
• Updated: 28/Nov/17 15:09
• Resolved: 28/Nov/17 15:09

Description

Parts of this have cropped up in a few tickets affecting CNFEs and inability to load processors. This is typically exacerbated by the inclusion of NiFi processors which also depend on NiFi Standard Services API NAR (typically for SSL Context Service). This can lead to problems when MiNiFi is started as the transformed flow is effectively a <1.2 version which does not have the bundling information established. Accordingly, in the case above where I bring a separate processor NAR with its associated versioned, services NAR, there are two instances which leads to a ghost implementation. For NiFI, this is resolved in the UI to select the desired version but we have no such facility in MiNiFi.

Issue Links

• incorporates: MINIFI-348 Schema validation error parsing Flow Configuration
• links to: GitHub Pull Request #99