[
https://issues.apache.org/jira/browse/NIFI-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-1052:
------------------------------
Fix Version/s: 0.5.0
> 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
> Fix For: 0.5.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)
