[
https://issues.apache.org/jira/browse/NIFI-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238356#comment-17238356
]
ASF subversion and git services commented on NIFI-8041:
-------------------------------------------------------
Commit 7ad9520079fdbe4efe47ed5b6248ec513fd0ca0b in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7ad9520 ]
NIFI-8041: Refactored API for stateless nifi so that calling
StatelessDataflow.trigger() returns an object that allows the caller to wait
for the result, cancel the result, etc. and then optionally acknowledge the
completion. This allows the caller to block the completion of
ProcessSession.commit() until it has handled the output of the dataflow
execution.
NIFI-8038: Fixed deadlock that can occur when updating Parameter Context
This closes #4684.
Signed-off-by: Bryan Bende <bbe...@apache.org>
> Allow stateless to be run asynchronously
> ----------------------------------------
>
> Key: NIFI-8041
> URL: https://issues.apache.org/jira/browse/NIFI-8041
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We should allow stateless nifi to be run asynchronously such that when a flow
> is running it can be canceled. Additionally, when the flow completes, we
> should not immediately commit the Process Session but rather give the caller
> a chance to acknowledge the FlowFiles or cancel/rollback.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
