You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2020/01/22 15:08:00 UTC

[jira] [Updated] (NIFI-6767) NiFi Registry URL does not get persisted properly if a port is not present

     [ https://issues.apache.org/jira/browse/NIFI-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Witt updated NIFI-6767:
---------------------------
    Summary: NiFi Registry URL does not get persisted properly if a port is not present  (was: NiFi Registry Config does not persist after a cluster restart)

> NiFi Registry URL does not get persisted properly if a port is not present
> --------------------------------------------------------------------------
>
>                 Key: NIFI-6767
>                 URL: https://issues.apache.org/jira/browse/NIFI-6767
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Flow Versioning
>    Affects Versions: 1.10.0, 1.9.2, 1.11.0
>            Reporter: John E Fortin
>            Assignee: Kristjan Antunovic
>            Priority: Major
>         Attachments: registry-bad.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After configuring the NiFi Registery and versioning flows the Registry works fine.  However, after restarting the NiFI cluster the Registry Config now has "https://null:-1" as the value for the Registry URL.  
> If I reconfigure the URL it works fine until the next Cluster restart.
> This has been happening since 1.9.1 (that I know of) and continues into 1.10
> It's not a show stopper, but is quite annoying



--
This message was sent by Atlassian Jira
(v8.3.4#803005)