From issues-return-97730-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Mon May 25 19:07:02 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3F05B18066D for ; Mon, 25 May 2020 21:07:02 +0200 (CEST) Received: (qmail 90942 invoked by uid 500); 25 May 2020 19:07:01 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 90905 invoked by uid 99); 25 May 2020 19:07:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 May 2020 19:07:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AEAFBE0101 for ; Mon, 25 May 2020 19:07:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 20FE9780589 for ; Mon, 25 May 2020 19:07:00 +0000 (UTC) Date: Mon, 25 May 2020 19:07:00 +0000 (UTC) From: "Eric Secules (Jira)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (NIFI-7489) resolveInheritedControllerServices doesn't connect all controller services MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Secules updated NIFI-7489: ------------------------------- Description: h1. Description When I download versioned flows from NiFi Registry, sometimes it does not connect processors to controller services even though one exists in scope and it has the same name as the one it was originally connected to. h1. Expected Behaviour NiFi downloads versioned process groups and connects external controller services correctly provided that a compatible controller service is available and has the same name. h1. Actual Behaviour NiFi downloads versioned flows but does not connect all external controller services. h1. Steps to reproduce: * Upload the attached template to your NiFi * Ensure the necessary Controller Services exist at the ROOT process group. ** DistributedMapCacheClientService ** AzureStorageCredentialsControllerService ** DistributedMapCacheServer * Resolve all warnings on processors, maybe need to connect the above controller services. * Start version control on "Inner Versioned Flow" * Start version control on "Outer Versioned Flow" * Clear Canvas * Delete and Recreate the Controller Services ** DistributedMapCacheClientService ** AzureStorageCredentialsControllerService ** DistributedMapCacheServer * Import "Outer Versioned Flow" from your registry You should observe that one processor in Inner Versioned Flow is invalid because it wasn't connected to an existing controller service and that the other processor is valid because by coincidence it shares the same dependency on an external controller service as the Outer Versioned Flow was: h1. Description When I download versioned flows from NiFi Registry, sometimes it does not connect processors to controller services even though one exists in scope and it has the same name as the one it was originally connected to. h1. Expected Behaviour NiFi downloads versioned process groups and connects external controller services correctly provided that a compatible controller service is available and has the same name. h1. Actual Behaviour NiFi downloads versioned flows but does not connect all external controller services. h1. Steps to reproduce: * Upload the attached template to your NiFi * Create the necessary Controller Services at the Root process group and manually connect them to the two processors here. ** DistributedMapCacheClientService ** AzureStorageCredentialsControllerService ** DistributedMapCacheServer * Start version control on "Inner Versioned Flow" * Start version control on "Outer Versioned Flow" * Clear Canvas * Delete and Recreate the Controller Services ** DistributedMapCacheClientService ** AzureStorageCredentialsControllerService ** DistributedMapCacheServer * Import "Outer Versioned Flow" from your registry You should observe that one processor in Inner Versioned Flow is invalid because it wasn't connected to an existing controller service and that the other processor is valid because by coincidence it shares the same dependency on an external controller service as the Outer Versioned Flow > resolveInheritedControllerServices doesn't connect all controller services > -------------------------------------------------------------------------- > > Key: NIFI-7489 > URL: https://issues.apache.org/jira/browse/NIFI-7489 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework, Flow Versioning > Affects Versions: 1.11.4 > Environment: Official NiFi Docker Container > Reporter: Eric Secules > Priority: Major > Attachments: externalServiceReference_Issue.xml > > > h1. Description > When I download versioned flows from NiFi Registry, sometimes it does not connect processors to controller services even though one exists in scope and it has the same name as the one it was originally connected to. > h1. Expected Behaviour > NiFi downloads versioned process groups and connects external controller services correctly provided that a compatible controller service is available and has the same name. > h1. Actual Behaviour > NiFi downloads versioned flows but does not connect all external controller services. > h1. Steps to reproduce: > * Upload the attached template to your NiFi > * Ensure the necessary Controller Services exist at the ROOT process group. > ** DistributedMapCacheClientService > ** AzureStorageCredentialsControllerService > ** DistributedMapCacheServer > * Resolve all warnings on processors, maybe need to connect the above controller services. > * Start version control on "Inner Versioned Flow" > * Start version control on "Outer Versioned Flow" > * Clear Canvas > * Delete and Recreate the Controller Services > ** DistributedMapCacheClientService > ** AzureStorageCredentialsControllerService > ** DistributedMapCacheServer > * Import "Outer Versioned Flow" from your registry > You should observe that one processor in Inner Versioned Flow is invalid because it wasn't connected to an existing controller service and that the other processor is valid because by coincidence it shares the same dependency on an external controller service as the Outer Versioned Flow -- This message was sent by Atlassian Jira (v8.3.4#803005)