[
https://issues.apache.org/jira/browse/NIFI-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855753#comment-17855753
]
Matt Burgess commented on NIFI-13196:
-------------------------------------
I certainly respect that view. I guess my only issue is because the community
is vibrant and large and diversified, it's difficult to say "we" definitively,
I think if community members or the users they support are "stuck" with 1.x for
a while, they will still want improvements in any aspect and will be willing to
maintain and be active on the 1.x branch (they are of course welcome to add
their own comments here or in the mailing list). Since there is no official
release of NiFi 2.0.0 yet, there are users in various industries that make
ample use of NiFi that have additional restrictions that would prevent them
from upgrading to a milestone release especially for a first major version
release. I'm not a proponent of making fundamental API changes in 1.x either,
but since this is a delegate method it just doesn't seem like a stability issue.
> 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)
