[
https://issues.apache.org/jira/browse/NIFI-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070596#comment-16070596
]
ASF GitHub Bot commented on NIFI-4131:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/1954
+1 LGTM, thanks for the fix! I wish we had the ability to check
connections upon validation, so we could prevent the user from starting the
processor in this situation, but an error message / bulletin will work just
fine until that happens.
Merging to master
> GenerateTableFetch - Add a warning when not correctly setting the connections
> -----------------------------------------------------------------------------
>
> Key: NIFI-4131
> URL: https://issues.apache.org/jira/browse/NIFI-4131
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Trivial
> Fix For: 1.4.0
>
>
> When using the GenerateTableFetch, I found myself into the following
> situation: using the processor as a source processor (no incoming connection)
> but setting the failure relationship back on the processor itself. With this
> setup the processor will never do anything and will not generate any kind of
> log message.
> I know it didn't make sense to use the failure relationship on a source
> processor and that the behavior is described in the documentation, but it
> could be useful to add a warning in such a situation (for people like me ;-)).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
