[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334727#comment-15334727
 ] 

ASF subversion and git services commented on NIFI-1829:
---

Commit 4723f8e24c83b3fda68a091be7deabfd84f2b40a in nifi's branch 
refs/heads/master from [~jskora]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4723f8e ]

NIFI-1829 - Create new DebugFlow processor.

Signed-off-by: Mike Moser 
This closes #458


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334730#comment-15334730
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/458


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334148#comment-15334148
 ] 

ASF subversion and git services commented on NIFI-1829:
---

Commit 19fcc40c82ea4417ce3a3917ce3b54c44826b4c6 in nifi's branch refs/heads/0.x 
from [~jskora]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=19fcc40 ]

NIFI-1829 - Create new DebugFlow processor.

Signed-off-by: Mike Moser 
This closes #458


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334096#comment-15334096
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/458
  
Completed review, latest changes look good, unit testing and integration 
testing worked as expected, code passes -Pcontrib-check.

+1 I will squash commits and merge to 0.x and master shortly.  Thanks 
@jskora.


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333904#comment-15333904
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/458
  
Ok, I think that last commit covers the review feedback.


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333748#comment-15333748
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r67341980
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.http.annotation.ThreadSafe;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+@ThreadSafe()
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "FlowFile"})
+@CapabilityDescription("The DebugFlow processor aids testing and debugging 
the FlowFile framework by allowing various "
++ "responses to be explicitly triggered in response to the receipt 
of a FlowFile or a timer event without a "
++ "FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test "
++ "various failure modes that can occur when a processor runs.\n"
++ "\n"
++ "When triggered, the processor loops through the appropriate 
response list (based on whether or not it "
++ "received a FlowFile).  A response is produced the configured 
number of times for each pass through its"
++ "response list, as long as the processor is running.\n"
++ "\n"
++ "Triggered by a FlowFile, the processor can produce the 
following responses."
++ "  1. transfer FlowFile to success relationship.\n"
++ "  2. transfer FlowFile to failure relationship.\n"
++ "  3. rollback the FlowFile without penalty.\n"
++ "  4. rollback the FlowFile and yield the context.\n"
++ "  5. rollback the FlowFile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "Triggered without a FlowFile, the processor can produce the 
following responses."
++ "  1. do nothing and return.\n"
++ "  2. throw an exception.\n"
++ "  3. yield the context.\n")
+public class DebugFlow extends AbstractProcessor {
+
+private final AtomicReference relationships = new 
AtomicReference<>();
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("FlowFiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new Relationship.Builder()
+.name("failure")
+.description("FlowFiles that failed to process.")
+.build();
+

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333679#comment-15333679
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r67335539
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.http.annotation.ThreadSafe;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+@ThreadSafe()
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "FlowFile"})
+@CapabilityDescription("The DebugFlow processor aids testing and debugging 
the FlowFile framework by allowing various "
++ "responses to be explicitly triggered in response to the receipt 
of a FlowFile or a timer event without a "
++ "FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test "
++ "various failure modes that can occur when a processor runs.\n"
++ "\n"
++ "When triggered, the processor loops through the appropriate 
response list (based on whether or not it "
++ "received a FlowFile).  A response is produced the configured 
number of times for each pass through its"
++ "response list, as long as the processor is running.\n"
++ "\n"
++ "Triggered by a FlowFile, the processor can produce the 
following responses."
++ "  1. transfer FlowFile to success relationship.\n"
++ "  2. transfer FlowFile to failure relationship.\n"
++ "  3. rollback the FlowFile without penalty.\n"
++ "  4. rollback the FlowFile and yield the context.\n"
++ "  5. rollback the FlowFile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "Triggered without a FlowFile, the processor can produce the 
following responses."
++ "  1. do nothing and return.\n"
++ "  2. throw an exception.\n"
++ "  3. yield the context.\n")
+public class DebugFlow extends AbstractProcessor {
+
+private final AtomicReference relationships = new 
AtomicReference<>();
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("FlowFiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new Relationship.Builder()
+.name("failure")
+.description("FlowFiles that failed to process.")
+.build();
+

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333675#comment-15333675
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r67335284
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.http.annotation.ThreadSafe;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+@ThreadSafe()
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "FlowFile"})
+@CapabilityDescription("The DebugFlow processor aids testing and debugging 
the FlowFile framework by allowing various "
++ "responses to be explicitly triggered in response to the receipt 
of a FlowFile or a timer event without a "
++ "FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test "
++ "various failure modes that can occur when a processor runs.\n"
++ "\n"
++ "When triggered, the processor loops through the appropriate 
response list (based on whether or not it "
++ "received a FlowFile).  A response is produced the configured 
number of times for each pass through its"
++ "response list, as long as the processor is running.\n"
++ "\n"
++ "Triggered by a FlowFile, the processor can produce the 
following responses."
++ "  1. transfer FlowFile to success relationship.\n"
++ "  2. transfer FlowFile to failure relationship.\n"
++ "  3. rollback the FlowFile without penalty.\n"
++ "  4. rollback the FlowFile and yield the context.\n"
++ "  5. rollback the FlowFile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "Triggered without a FlowFile, the processor can produce the 
following responses."
++ "  1. do nothing and return.\n"
++ "  2. throw an exception.\n"
++ "  3. yield the context.\n")
--- End diff --

Split out to additional details page.


> 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 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15332389#comment-15332389
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r67230976
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.http.annotation.ThreadSafe;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+@ThreadSafe()
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "FlowFile"})
+@CapabilityDescription("The DebugFlow processor aids testing and debugging 
the FlowFile framework by allowing various "
++ "responses to be explicitly triggered in response to the receipt 
of a FlowFile or a timer event without a "
++ "FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test "
++ "various failure modes that can occur when a processor runs.\n"
++ "\n"
++ "When triggered, the processor loops through the appropriate 
response list (based on whether or not it "
++ "received a FlowFile).  A response is produced the configured 
number of times for each pass through its"
++ "response list, as long as the processor is running.\n"
++ "\n"
++ "Triggered by a FlowFile, the processor can produce the 
following responses."
++ "  1. transfer FlowFile to success relationship.\n"
++ "  2. transfer FlowFile to failure relationship.\n"
++ "  3. rollback the FlowFile without penalty.\n"
++ "  4. rollback the FlowFile and yield the context.\n"
++ "  5. rollback the FlowFile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "Triggered without a FlowFile, the processor can produce the 
following responses."
++ "  1. do nothing and return.\n"
++ "  2. throw an exception.\n"
++ "  3. yield the context.\n")
--- End diff --

I wonder if there's an abbreviated version of the doc for capability 
description, and move this out to an additional details page 


> 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 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15332383#comment-15332383
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user mosermw commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r67230370
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.http.annotation.ThreadSafe;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+@ThreadSafe()
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "FlowFile"})
+@CapabilityDescription("The DebugFlow processor aids testing and debugging 
the FlowFile framework by allowing various "
++ "responses to be explicitly triggered in response to the receipt 
of a FlowFile or a timer event without a "
++ "FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test "
++ "various failure modes that can occur when a processor runs.\n"
++ "\n"
++ "When triggered, the processor loops through the appropriate 
response list (based on whether or not it "
++ "received a FlowFile).  A response is produced the configured 
number of times for each pass through its"
++ "response list, as long as the processor is running.\n"
++ "\n"
++ "Triggered by a FlowFile, the processor can produce the 
following responses."
++ "  1. transfer FlowFile to success relationship.\n"
++ "  2. transfer FlowFile to failure relationship.\n"
++ "  3. rollback the FlowFile without penalty.\n"
++ "  4. rollback the FlowFile and yield the context.\n"
++ "  5. rollback the FlowFile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "Triggered without a FlowFile, the processor can produce the 
following responses."
++ "  1. do nothing and return.\n"
++ "  2. throw an exception.\n"
++ "  3. yield the context.\n")
+public class DebugFlow extends AbstractProcessor {
+
+private final AtomicReference relationships = new 
AtomicReference<>();
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("FlowFiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new Relationship.Builder()
+.name("failure")
+.description("FlowFiles that failed to process.")
+.build();
+

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15332380#comment-15332380
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user mosermw commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r67230167
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,499 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.http.annotation.ThreadSafe;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+@ThreadSafe()
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "FlowFile"})
+@CapabilityDescription("The DebugFlow processor aids testing and debugging 
the FlowFile framework by allowing various "
++ "responses to be explicitly triggered in response to the receipt 
of a FlowFile or a timer event without a "
++ "FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test "
++ "various failure modes that can occur when a processor runs.\n"
++ "\n"
++ "When triggered, the processor loops through the appropriate 
response list (based on whether or not it "
++ "received a FlowFile).  A response is produced the configured 
number of times for each pass through its"
++ "response list, as long as the processor is running.\n"
++ "\n"
++ "Triggered by a FlowFile, the processor can produce the 
following responses."
++ "  1. transfer FlowFile to success relationship.\n"
++ "  2. transfer FlowFile to failure relationship.\n"
++ "  3. rollback the FlowFile without penalty.\n"
++ "  4. rollback the FlowFile and yield the context.\n"
++ "  5. rollback the FlowFile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "Triggered without a FlowFile, the processor can produce the 
following responses."
++ "  1. do nothing and return.\n"
++ "  2. throw an exception.\n"
++ "  3. yield the context.\n")
--- End diff --

Formatting with \n doesn't work inside a CapabilityDescription annotation.  
It just gets smashed together.  If you are OK with that @jskora then we can 
leave it.


> 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
>
>
> 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331884#comment-15331884
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on the issue:

https://github.com/apache/nifi/pull/458
  
I don't mind even a little! Thanks @mosermw


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331876#comment-15331876
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/458
  
@trkurc ok, in order to get 0.7.0 as soon as possible, would you mind if 
another committer took over reviewing?


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331877#comment-15331877
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/458
  
I will review.


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331845#comment-15331845
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on the issue:

https://github.com/apache/nifi/pull/458
  
It looks like the issues I had were addressed, but I won't have a chance to 
dive in deeper until Saturday, maybe


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331839#comment-15331839
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on the issue:

https://github.com/apache/nifi/pull/458
  
Not until this weekend
On Jun 15, 2016 4:30 PM, "Joe Percivall"  wrote:

> @jskora  rebased and addressed comments,
> @trkurc  are you able to finish reviewing this
> for 0.7.0?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or mute
> the thread
> 

> .
>



> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[Bryan Bende (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331836#comment-15331836
 ] 

Bryan Bende commented on NIFI-1829:
---

This ticket is tagged for 0.7.0 and has a PR, should it be set to "Patch 
Available" or is it not ready for 0.7 ? 

> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331834#comment-15331834
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/458
  
@jskora rebased and addressed comments, @trkurc are you able to finish 
reviewing this for 0.7.0?


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311796#comment-15311796
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r65487473
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,414 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ProcessorLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "flowfile"})
+@CapabilityDescription("This processor aids in the testing and debugging 
of the flowfile framework by allowing "
++ "a developer or flow manager to force various responses to a 
flowfile.  In response to a receiving a flowfile "
++ "it can route to the success or failure relationships, rollback, 
rollback and yield, rollback with penalty, "
++ "or throw an exception.  In addition, if using a timer based 
scheduling strategy, upon being triggered without "
++ "a flowfile, it can be configured to throw an exception,  when 
triggered without a flowfile.\n"
++ "\n"
++ "The 'iterations' properties, such as \"Success iterations\", 
configure how many times each response should occur "
++ "in succession before moving on to the next response within the 
group of flowfile responses or no flowfile"
++ "responses.\n"
++ "\n"
++ "The order of responses when a flow file is received are:"
++ "  1. transfer flowfile to success relationship.\n"
++ "  2. transfer flowfile to failure relationship.\n"
++ "  3. rollback the flowfile without penalty.\n"
++ "  4. rollback the flowfile and yield the context.\n"
++ "  5. rollback the flowfile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "The order of responses when no flow file is received are:"
++ "  1. yield the context.\n"
++ "  2. throw an exception.\n"
++ "  3. do nothing and return.\n"
++ "\n"
++ "By default, the processor is configured to perform each 
response one time.  After processing the list of "
++ "responses it will resume from the top of the list.\n"
++ "\n"
++ "To suppress any response, it's value can be set to zero (0) and 
no responses of that type will occur during "
++ "processing.")
+public class DebugFlow extends AbstractProcessor {
+
+private Set relationships = null;
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("Flowfiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311793#comment-15311793
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r65487334
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,414 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ProcessorLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "flowfile"})
+@CapabilityDescription("This processor aids in the testing and debugging 
of the flowfile framework by allowing "
++ "a developer or flow manager to force various responses to a 
flowfile.  In response to a receiving a flowfile "
++ "it can route to the success or failure relationships, rollback, 
rollback and yield, rollback with penalty, "
++ "or throw an exception.  In addition, if using a timer based 
scheduling strategy, upon being triggered without "
++ "a flowfile, it can be configured to throw an exception,  when 
triggered without a flowfile.\n"
++ "\n"
++ "The 'iterations' properties, such as \"Success iterations\", 
configure how many times each response should occur "
++ "in succession before moving on to the next response within the 
group of flowfile responses or no flowfile"
++ "responses.\n"
++ "\n"
++ "The order of responses when a flow file is received are:"
++ "  1. transfer flowfile to success relationship.\n"
++ "  2. transfer flowfile to failure relationship.\n"
++ "  3. rollback the flowfile without penalty.\n"
++ "  4. rollback the flowfile and yield the context.\n"
++ "  5. rollback the flowfile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "The order of responses when no flow file is received are:"
++ "  1. yield the context.\n"
++ "  2. throw an exception.\n"
++ "  3. do nothing and return.\n"
++ "\n"
++ "By default, the processor is configured to perform each 
response one time.  After processing the list of "
++ "responses it will resume from the top of the list.\n"
++ "\n"
++ "To suppress any response, it's value can be set to zero (0) and 
no responses of that type will occur during "
++ "processing.")
+public class DebugFlow extends AbstractProcessor {
+
+private Set relationships = null;
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("Flowfiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311771#comment-15311771
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user jskora commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r65486064
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,414 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ProcessorLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "flowfile"})
+@CapabilityDescription("This processor aids in the testing and debugging 
of the flowfile framework by allowing "
++ "a developer or flow manager to force various responses to a 
flowfile.  In response to a receiving a flowfile "
++ "it can route to the success or failure relationships, rollback, 
rollback and yield, rollback with penalty, "
++ "or throw an exception.  In addition, if using a timer based 
scheduling strategy, upon being triggered without "
++ "a flowfile, it can be configured to throw an exception,  when 
triggered without a flowfile.\n"
--- End diff --

Agreed.


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308267#comment-15308267
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r65234934
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,414 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ProcessorLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "flowfile"})
+@CapabilityDescription("This processor aids in the testing and debugging 
of the flowfile framework by allowing "
++ "a developer or flow manager to force various responses to a 
flowfile.  In response to a receiving a flowfile "
++ "it can route to the success or failure relationships, rollback, 
rollback and yield, rollback with penalty, "
++ "or throw an exception.  In addition, if using a timer based 
scheduling strategy, upon being triggered without "
++ "a flowfile, it can be configured to throw an exception,  when 
triggered without a flowfile.\n"
++ "\n"
++ "The 'iterations' properties, such as \"Success iterations\", 
configure how many times each response should occur "
++ "in succession before moving on to the next response within the 
group of flowfile responses or no flowfile"
++ "responses.\n"
++ "\n"
++ "The order of responses when a flow file is received are:"
++ "  1. transfer flowfile to success relationship.\n"
++ "  2. transfer flowfile to failure relationship.\n"
++ "  3. rollback the flowfile without penalty.\n"
++ "  4. rollback the flowfile and yield the context.\n"
++ "  5. rollback the flowfile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "The order of responses when no flow file is received are:"
++ "  1. yield the context.\n"
++ "  2. throw an exception.\n"
++ "  3. do nothing and return.\n"
++ "\n"
++ "By default, the processor is configured to perform each 
response one time.  After processing the list of "
++ "responses it will resume from the top of the list.\n"
++ "\n"
++ "To suppress any response, it's value can be set to zero (0) and 
no responses of that type will occur during "
++ "processing.")
+public class DebugFlow extends AbstractProcessor {
+
+private Set relationships = null;
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("Flowfiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308223#comment-15308223
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r65231261
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,414 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ProcessorLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "flowfile"})
+@CapabilityDescription("This processor aids in the testing and debugging 
of the flowfile framework by allowing "
++ "a developer or flow manager to force various responses to a 
flowfile.  In response to a receiving a flowfile "
++ "it can route to the success or failure relationships, rollback, 
rollback and yield, rollback with penalty, "
++ "or throw an exception.  In addition, if using a timer based 
scheduling strategy, upon being triggered without "
++ "a flowfile, it can be configured to throw an exception,  when 
triggered without a flowfile.\n"
++ "\n"
++ "The 'iterations' properties, such as \"Success iterations\", 
configure how many times each response should occur "
++ "in succession before moving on to the next response within the 
group of flowfile responses or no flowfile"
++ "responses.\n"
++ "\n"
++ "The order of responses when a flow file is received are:"
++ "  1. transfer flowfile to success relationship.\n"
++ "  2. transfer flowfile to failure relationship.\n"
++ "  3. rollback the flowfile without penalty.\n"
++ "  4. rollback the flowfile and yield the context.\n"
++ "  5. rollback the flowfile with penalty.\n"
++ "  6. throw an exception.\n"
++ "\n"
++ "The order of responses when no flow file is received are:"
++ "  1. yield the context.\n"
++ "  2. throw an exception.\n"
++ "  3. do nothing and return.\n"
++ "\n"
++ "By default, the processor is configured to perform each 
response one time.  After processing the list of "
++ "responses it will resume from the top of the list.\n"
++ "\n"
++ "To suppress any response, it's value can be set to zero (0) and 
no responses of that type will occur during "
++ "processing.")
+public class DebugFlow extends AbstractProcessor {
+
+private Set relationships = null;
+
+static final Relationship REL_SUCCESS = new Relationship.Builder()
+.name("success")
+.description("Flowfiles processed successfully.")
+.build();
+static final Relationship REL_FAILURE = new 

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308216#comment-15308216
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on a diff in the pull request:

https://github.com/apache/nifi/pull/458#discussion_r65230520
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java
 ---
@@ -0,0 +1,414 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ProcessorLog;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+@EventDriven()
+@Tags({"test", "debug", "processor", "utility", "flow", "flowfile"})
+@CapabilityDescription("This processor aids in the testing and debugging 
of the flowfile framework by allowing "
++ "a developer or flow manager to force various responses to a 
flowfile.  In response to a receiving a flowfile "
++ "it can route to the success or failure relationships, rollback, 
rollback and yield, rollback with penalty, "
++ "or throw an exception.  In addition, if using a timer based 
scheduling strategy, upon being triggered without "
++ "a flowfile, it can be configured to throw an exception,  when 
triggered without a flowfile.\n"
--- End diff --

I think the last "when triggered ..." is redundant


> 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308157#comment-15308157
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

Github user trkurc commented on the pull request:

https://github.com/apache/nifi/pull/458
  
reviewing 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)

[jira] [Commented] (NIFI-1829) Create FlowDebugger processor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293754#comment-15293754
 ] 

ASF GitHub Bot commented on NIFI-1829:
--

GitHub user jskora opened a pull request:

https://github.com/apache/nifi/pull/458

NIFI-1829 - Create new DebugFlow processor.

* Create DebugFlow processor for use in testing and troubleshooting the 
processor framework.

* 0.x - commits as is.
* 1.x - in o.a.n.p.s.DebugFlow.java replace ProcessorLog references with 
ComponentLog.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jskora/nifi NIFI-1829

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/458.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #458


commit 3c7ac5b24a8d9ffd6188482fb50d89b43d6960d0
Author: Joe Skora 
Date:   2016-05-20T15:25:03Z

NIFI-1829 - Create new DebugFlow processor.




> 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)