[
https://issues.apache.org/jira/browse/NIFI-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855772#comment-17855772
]
Matt Burgess commented on NIFI-13196:
-------------------------------------
Totally agree, everyone needs 2.0, just aiming to support the folks that can't
upgrade yet. The new UI and other framework improvements and AI additions are
going to keep NiFi essential and help users moving forward, But if some of the
improvements can't be applied to 1.x I'm thinking there are users that can only
see it as the light at the end of the tunnel and not solving the problem(s)
they're having at present, whether they be bugs or performance issues.
Fundamental API changes need to be closely inspected, especially in 1.x, but
this one is for a reason and I think it could benefit every user.
> Add a new isAutoTerminated(Relationship) method to ProcessContext
> -----------------------------------------------------------------
>
> Key: NIFI-13196
> URL: https://issues.apache.org/jira/browse/NIFI-13196
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently a Processor has no way of determining whether or not a Relationship
> is auto-terminated. There are cases where a Processor forks an incoming
> FlowFile and updates it (in a potentially expensive manner) and then
> transfers it to a Relationship that is auto-terminated.
> We should add the ability to determine whether or not a given relationship is
> auto-terminated so that we can be more efficient
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
