[
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314626#comment-15314626
]
ASF GitHub Bot commented on NIFI-1829:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/458
I'm having trouble understanding the naming convention here. "DebugFlow"
would indicate that it is debugging the flow that you are putting together, but
the comment states "Create DebugFlow processor for use in testing and
troubleshooting the processor framework." So it appears that the desire is to
debug the framework?
I also wonder if this is something that should be in the nifi codebase, as
it really seems like a niche processor that is intended to test very specific
things and not something that we would expect typical users to use. I may be
wrong, but would GitHub be a more appropriate place for this?
> 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)
