[
https://issues.apache.org/jira/browse/NIFI-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013031#comment-16013031
]
ASF subversion and git services commented on NIFI-3904:
-------------------------------------------------------
Commit 3a0004a665c2f7bebe10ec54db08e2b8c7e2804f in nifi's branch
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3a0004a ]
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)
