[
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314823#comment-15314823
]
ASF GitHub Bot commented on NIFI-1829:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/458
The name isn't great but not sure what would be better. It is indeed a
debugger for the framework and less so for a flow. It is perhaps good to call
it 'CreateChaos'. That said i personally think this is a great idea to have in
the build and part of the standard processors. It would only be used by power
users or curious types. And for everyone else it is a noop. But it could make
it easier for us to demonstrate the evil effects of constant exceptions in a
flow and do interesting regression checks on various infrastructures. There is
admittedly probably a better place for this but with the upcoming nar registry
work we can tackle that then.
> Create FlowDebugger processor
> -----------------------------
>
> Key: NIFI-1829
> URL: https://issues.apache.org/jira/browse/NIFI-1829
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joe Skora
> Assignee: Joe Skora
> Priority: Minor
> Fix For: 1.0.0, 0.7.0
>
>
> The FlowDebugger processor allows a variety of Processor responses and
> failures to be simulated for testing, debugging, and troubleshooting the
> framework.
> Responses it can produce on receipt of a flowfile include Transfer to
> Success, Transfer to Failure, Rollback without Penalty, Rollback and Yield,
> Rollback with Penalty, and Throw an Exception. The properties indicate how
> many times that response should be thrown, for example if configured with
> Success=10 and Failure=40, it will transfer the first 10 flowfiles to
> Success, transfer the next 40 to Failure, and then repeat.
> Similarly, responses it can produce when triggered without a flowfile include
> Throw an Exception, Yield, and Return (do nothing).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
