[
https://issues.apache.org/jira/browse/NIFI-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505208#comment-16505208
]
ASF GitHub Bot commented on NIFI-5274:
--------------------------------------
Github user mosermw commented on the issue:
https://github.com/apache/nifi/pull/2767
One never knows how a dataflow manager will design their flow, so I was
just trying to cover all bases. I don't think a downstream consumer would
notice that the failure files were penalized, but if someone did loop their
failure relationship, they would certainly notice if a failed file wan't
penalized.
I can remove the call to penalize.
> ReplaceText can product StackOverflowError which causes admin yield
> -------------------------------------------------------------------
>
> Key: NIFI-5274
> URL: https://issues.apache.org/jira/browse/NIFI-5274
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.6.0
> Reporter: Michael Moser
> Assignee: Michael Moser
> Priority: Major
>
> Regex Replace mode can easily produce StackOverflowError. Certain regular
> expressions are implemented using recursion, which when used on large input
> text can cause StackOverflowError. This causes the ReplaceText processor to
> rollback and admin yield, which causes the input flowfile to get stuck in the
> input queue.
> We should be able to catch this condition and route the flowfile to failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
