From issues-return-84036-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Tue Sep 3 15:33:04 2019 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 7F0BB180637 for ; Tue, 3 Sep 2019 17:33:04 +0200 (CEST) Received: (qmail 92430 invoked by uid 500); 3 Sep 2019 17:46:18 -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 92268 invoked by uid 99); 3 Sep 2019 17:46:17 -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; Tue, 03 Sep 2019 17:46:17 +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 AD099E2CC6 for ; Tue, 3 Sep 2019 15:33:01 +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 6141E78074B for ; Tue, 3 Sep 2019 15:33:00 +0000 (UTC) Date: Tue, 3 Sep 2019 15:33:00 +0000 (UTC) From: "ASF subversion and git services (Jira)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-6028) Upgrading NiFi can put versioned flows into a conflict state 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-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921518#comment-16921518 ] ASF subversion and git services commented on NIFI-6028: ------------------------------------------------------- Commit 180a188096905ec3c599f45a4c0235778951fb7c in nifi's branch refs/heads/master from Bryan Bende [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=180a188 ] NIFI-6028 Protect against null VersionedComponent when finding relevant process group This closes #3686. Signed-off-by: Mark Payne > Upgrading NiFi can put versioned flows into a conflict state > ------------------------------------------------------------ > > Key: NIFI-6028 > URL: https://issues.apache.org/jira/browse/NIFI-6028 > Project: Apache NiFi > Issue Type: Bug > Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1 > Reporter: Bryan Bende > Assignee: Mark Payne > Priority: Major > Labels: SDLC > Fix For: 1.10.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > When you upgrade NiFi, existing processors may have new properties and relationships. If any of those processors are part of a versioned flow then these changes will trigger a local modification indicating that a new version needs to be saved to registry to track the new properties or relationships. > The issue is when you have multiple environments... > * Start in dev with NiFi version X > * Upgrade dev to NiFi version Y > * Now commit versioned PGs in dev that had local changes > * Go to staging and upgrade NiFi to version Y > * The versioned PGs are now in conflict because there is an upgrade available, but there are local changes detected from upgrading NiFI, even though these are the same changes available in the upgrade -- This message was sent by Atlassian Jira (v8.3.2#803003)