[
https://issues.apache.org/jira/browse/NIFI-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316700#comment-15316700
]
ASF GitHub Bot commented on NIFI-1052:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/499
NIFI-1052: Added "Ghost" Processors, Reporting Tasks, Controller Services
If we try to create a component for which the NAR is missing, we previously
would throw an Exception that would result in NiFi not starting up. We changed
this so that we instead create a "Ghost" implementation that will be invalid an
explain that the component could not be created. This allows NiFi at least to
start, so that users can continue to use the NiFi instance.
This ticket also includes fixes to the ReportingTaskResource, as those were
necessary to test this.
Note that if a component is missing, all properties are marked as
'sensitive' simply because we don't know whether or not the property truly is
sensitive, and it is better to show the value as sensitive than to assume that
it is not. Unfortunately, this means that the actual property value can't be
seen unless the correct component is restored to the lib/ directory.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1052
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/499.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 #499
----
commit d86fd959f3ba20facdfc207b80da5fb48feaf379
Author: Mark Payne <[email protected]>
Date: 2016-06-03T23:41:43Z
NIFI-1052: Added Ghost Processors, Ghost Reporting Tasks, Ghost Controller
Services
----
> Improve flow behavior on refactored processor names/packages
> ------------------------------------------------------------
>
> Key: NIFI-1052
> URL: https://issues.apache.org/jira/browse/NIFI-1052
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: sumanth chinthagunta
> Assignee: Joseph Witt
> Fix For: 0.7.0
>
>
> My case is simple and easy to reproduce:
> 1. Create a flow with custom processor (e.g. abc.MyProcesser )
> 2. Make sure flow is working. Then stop the server.
> 3. Replace nar in lib with new nar after refactoring processor's package (
> e.g., xzy.MyProcesser)
> 4. When you try to start nifi , it fails with error in the log saying class
> not found ( obviously coz deployed flow is still looking for old class)
> My expectation is system should at least start and only throw error when
> user try to start a flow that that had reference to class(processor) which
> is no more available in the newly deployed nar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
