[
https://issues.apache.org/jira/browse/NIFI-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614989#comment-16614989
]
ASF subversion and git services commented on NIFI-5577:
-------------------------------------------------------
Commit 14729be837109af9fe986d61a0b3abcb2288672a in nifi's branch
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=14729be ]
NIFI-5577 Fixing update method in NaiveRevisionManager so that failed updates
don't change the revision
This closes #2995.
Signed-off-by: Mark Payne <[email protected]>
> Component revision number can be incorrectly changed during a failed update
> ---------------------------------------------------------------------------
>
> Key: NIFI-5577
> URL: https://issues.apache.org/jira/browse/NIFI-5577
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.7.1
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> When an update of a component throws an exception, the revision number is
> incorrectly set to whatever the client passed in, and since clients are
> allowed to keep making requests without the latest revision number this means
> the revision number can incorrectly set back to some lower number.
> Steps to reproduce...
> * Create a GenerateFlowFile processor and get back revision 1
> * Change the name three times and get to revision 4
> * Submit an update where the revision is 1 and set the state to RUNNING
> which should fail because the component is invalid
> * Perform a GET for the processors and notice the revision is now 1 and not 4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
