[
https://issues.apache.org/jira/browse/MINIFI-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220873#comment-16220873
]
Aldrin Piri commented on MINIFI-408:
------------------------------------
In lieu of getting into the internals of NiFi and the extension manager, I will
attempt to augment the transformer to incorporate values of the associated
bundles in the lib directory when the resultant flow is generated. This might
also aid in alleviating MINIFI-348.
> Improve handling of bundle versioning in NARs with other NARs as dependencies
> -----------------------------------------------------------------------------
>
> Key: MINIFI-408
> URL: https://issues.apache.org/jira/browse/MINIFI-408
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.2.0
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
> Priority: Blocker
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
