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

ASF GitHub Bot commented on NIFI-3904:
--------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi/pull/1808

    NIFI-3904 Adding logic to only reload when incoming bundle is differe…

    …nt and to use additional URLs from spec component
    
    NIFI-3908 Changing UI to submit filterType for CSs and filter for 
processors and reporting tasks


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

    $ git pull https://github.com/bbende/nifi NIFI-3904

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

    https://github.com/apache/nifi/pull/1808.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 #1808
    
----
commit 3ac6a887c9d7c5473fd94b0aa12ade756496cbbd
Author: Bryan Bende <[email protected]>
Date:   2017-05-16T17:52:10Z

    NIFI-3904 Adding logic to only reload when incoming bundle is different and 
to use additional URLs from spec component
    NIFI-3908 Changing UI to submit filterType for CSs and filter for 
processors and reporting tasks

----


> Updating component can unnecessarily reload component
> -----------------------------------------------------
>
>                 Key: NIFI-3904
>                 URL: https://issues.apache.org/jira/browse/NIFI-3904
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>             Fix For: 1.3.0
>
>
> StandardProcessorDAO, StandardControllerServiceDAO, and 
> StandardReportingTaskDAO all have a similar updateBundle that checks if the 
> incoming BundleDTO is not null on an update, and if so performs a reload of 
> the component.
> There are two issues here... 
> The first is that the reload should only be performed if the incoming bundle 
> coordinate is different than the existing bundle coordinate.
> The second is that when the reload is performed, it should retain the 
> appropriate additional classpath resources in the new classloader.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to