You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/15 17:01:00 UTC

[jira] [Commented] (NIFI-6036) If a Processor is intended to be running but is invalid when NiFi starts, it cannot be udpated.

    [ https://issues.apache.org/jira/browse/NIFI-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769506#comment-16769506 ] 

ASF subversion and git services commented on NIFI-6036:
-------------------------------------------------------

Commit b508d6bfbc2b6a68fe2ab152de96611f06a8724a in nifi's branch refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b508d6b ]

NIFI-6033, NIFI-6034, NIFI-6035, NIFI-6036, NIFI-6037: Fixed bugs that were found during 1.9.0-RC1 validation. If multiple FlowFiles were written to same Content Claim, and a Processor attempted to read two of them wi within a single session, it would seek to the wrong part of the content or else throw a ContentNotFoundException. Updated logic for considering a processor to be 'running' / having 'active threads' if the processor is invalid upon NiFi restart but scheduled to run. Fixed NPE in FreeFormTextWriter. If MergeRecord reaches minimum number of records, flush writer after writing content out so that its minimum size can accurately be checked.

This closes #3309.

Signed-off-by: Bryan Bende <bb...@apache.org>


> 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)