nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Grigorjan (Jira)" <j...@apache.org>
Subject [jira] [Created] (NIFI-6651) Connections overlaps if directed to another already connected processor
Date Wed, 11 Sep 2019 09:56:00 GMT
Arthur Grigorjan created NIFI-6651:
--------------------------------------

             Summary: Connections overlaps if directed to another already connected processor
                 Key: NIFI-6651
                 URL: https://issues.apache.org/jira/browse/NIFI-6651
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core UI
    Affects Versions: 1.9.2
         Environment: version: "3"
services:
  zookeeper:
    hostname: zookeeper2
    container_name: zookeeper2
    image: 'bitnami/zookeeper:latest'
    environment:
      - ALLOW_ANONYMOUS_LOGIN=yes
  nifi:
    image: apache/nifi:1.9.2
    ports:
      - 8080 # Unsecured HTTP Web Port
    environment:
      - NIFI_WEB_HTTP_PORT=8080
      - NIFI_CLUSTER_IS_NODE=true
      - NIFI_CLUSTER_NODE_PROTOCOL_PORT=8082
      - NIFI_ZK_CONNECT_STRING=zookeeper2:2181
      - NIFI_ELECTION_MAX_WAIT=1 min
            Reporter: Arthur Grigorjan
         Attachments: nifi-overlapping-connection-bug.gif

When a connection from processor A to B is redirected from A to C and A to C already has a
connection, then the two connections overlap. The user is not able to see that there are multiple
connections. This problem doesn't occur when creating a new connection from A to C (see GIF
attached).

 

The path of a connection should be calulated the same way when redirecting a connection as
it is when creating a new connection. 

 

Besides:

Why is it not allowed to delete a connection of a running source but to redirect it to another
destination?



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message