[
https://issues.apache.org/jira/browse/NIFI-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503885#comment-16503885
]
ASF GitHub Bot commented on NIFI-5274:
--------------------------------------
Github user mosermw commented on the issue:
https://github.com/apache/nifi/pull/2767
I'm not sure I understand what your suggestion is @joewitt. Would you
clarify for me? Should I code it to catch StackOverflowError, which is the use
case that I need to handle cleanly?
The code pattern I used here has worked really well for me in custom
processors to avoid yield/rollback on exceptions caused by flowfile content,
while maintaining a desired yield/rollback on framework exceptions in other
situations.
> 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)
