[
https://issues.apache.org/jira/browse/NIFI-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503839#comment-16503839
]
ASF GitHub Bot commented on NIFI-5274:
--------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/nifi/pull/2767
mvn package -P contrib-check passes,
code looks good.
The question that comes to my mind is if this is following some
'recommended' way of handling these exceptions, and should that be documented
or referenced. But I haven't seen any other processor document it's yield v.
fail strategy.
+1 fwiw
> 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)
