nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-408) Improve handling of bundle versioning in NARs with other NARs as dependencies
Date Mon, 13 Nov 2017 20:42:00 GMT

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

ASF GitHub Bot commented on MINIFI-408:
---------------------------------------

GitHub user apiri opened a pull request:

    https://github.com/apache/nifi-minifi/pull/99

    MINIFI-408 - Perform automated determination of compatible bundles

    MINIFI-408 - Perform automated determination of compatible bundles for flow startup. 
This seeks to provide a MiNiFi friendly process for
    handling those cases where NiFi would ghost a component and allow a user
    to select a specific bundle in the UI.
    
    MINIFI-348 - Removes validation warnings on startup as bundling
    information is evaluated and applied before starting the MiNiFi process.
    
    Thank you for submitting a contribution to Apache NiFi - MiNiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are
trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [X] Has your PR been rebased against the latest commit within the target branch (typically
master)?
    
    - [X] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check
clean install at the root nifi-minifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [-] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?

    - [-] If applicable, have you updated the LICENSE file, including the main LICENSE file
under minifi-assembly?
    - [-] If applicable, have you updated the NOTICE file, including the main NOTICE file
found under minifi-assembly?
    
    ### For documentation related changes:
    - [-] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apiri/nifi-minifi minifi-408-final

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-minifi/pull/99.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #99
    
----
commit d003cdb628023c24ee58216906ff8605d48169e4
Author: Aldrin Piri <aldrin@apache.org>
Date:   2017-11-10T20:57:29Z

    MINIFI-408 - Perform automated determination of compatible bundles for
    processor startup.  This seeks to provide a MiNiFi friendly process for
    handling those cases where NiFi would ghost a component and allow a user
    to select a specific bundle in the UI.
    
    MINIFI-348 - Removes validation warnings on startup as bundling
    information is evaluated and applied before starting the MiNiFi process.

----


> 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)

Mime
View raw message