You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/10/22 03:30:27 UTC

[jira] [Created] (NIFI-1052) Improve flow behavior on refactored processor names/packages

Joseph Witt created NIFI-1052:
---------------------------------

             Summary: 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


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)