[
https://issues.apache.org/jira/browse/NIFI-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775967#comment-16775967
]
Joseph Percivall commented on NIFI-6036:
----------------------------------------
[~markap14] do we know the affects version here?
Assuming 1.8 is affected, I'm looking at backport this fix. The PR is a
combination of multiple different issues, not all of which I want to backport.
What changes in the PR are for fixing this issue?
> If a Processor is intended to be running but is invalid when NiFi starts, it
> cannot be udpated.
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-6036
> URL: https://issues.apache.org/jira/browse/NIFI-6036
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.9.0
>
>
> To reproduce, create a GetFile processor and point it to `./data` and create
> that directory. Start the processor. Stop NiFi and rename the directory.
> Start NiFi again. On restart, the Processor will be invalid. If you rename
> the directory back to `./data` then the processor will become valid and run.
> However, if instead you attempt to update the Processor to point to a
> different directory, it will give an error saying that the Processor cannot
> be updated because it is not stopped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
