[
https://issues.apache.org/jira/browse/NIFI-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908624#comment-14908624
]
Rob Moran commented on NIFI-891:
--------------------------------
In the UI I’d recommend not allowing the user to create the connection at all.
Interaction can be the same as when attempting to create a connection to an
Input Port. You see the red dotted line and do not see the green border around
the target.
More awareness/additional feedback could be provided to the user as well. For
example, update the add connection icon to a version with a red slash through
it as they drag over the target. If they attempt to “drop” the connection,
prompt with a dialog stating why it can’t be done.
For pre-existing connections once the feature is implemented, render the
processor invalid and explain how to address in a tooltip. Would be nice to
expand tooltip functionality and provide follow on action directly from them
(e.g., _Remove connection_)
> Provide mechanisms to handle processors that do not take input connections
> --------------------------------------------------------------------------
>
> Key: NIFI-891
> URL: https://issues.apache.org/jira/browse/NIFI-891
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Extensions
> Reporter: Aldrin Piri
>
> This is the "other half" of functionality of NIFI-810.
> Some processors (typically those providing List, Get, Listen functionality)
> take no input connections which can be confusing to users as their is no
> indication and files will endlessly queue.
> Ideally, processors could be registered as invalid should they have a
> connection where they will not consume any files. Ideally, the UI will would
> prevent the connection from even making these connections.
> Processors that do not consume messages could also make use of an annotation
> akin to @IgnoresInput
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
