[
https://issues.apache.org/jira/browse/NIFI-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009203#comment-17009203
]
Kristjan Antunovic edited comment on NIFI-6767 at 1/6/20 10:28 PM:
-------------------------------------------------------------------
[~bbende] I managed to replicate this issue. Found the bug in following method:
{code:java}
StandardFlowRegistryClient@addFlowRegistry
{code}
The method saves domains in this format: http://domain.com:-1 or
https://domain.com:-1 if you are using http or https. If you than restart NiFi
the *registryUri* parameter comes in as such: *https://domain.com:-1*
The trailing *:-1* results in the invalid URI object that is being created in
the first line. When calling *getHost()* on this URI it will return *null* and
persist it again to flow file thus corrupting your URL.
I was able to replicate this pretty easily with just simple setup. Add registry
to nifi, restart it and the URL is gone.
was (Author: superkool):
[~bbende] I managed to replicate this issue. Found the bug in following method:
{code:java}
StandardFlowRegistryClient@addFlowRegistry
{code}
> NiFi Registry Config does not persist after a cluster restart
> -------------------------------------------------------------
>
> 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
> Reporter: John E Fortin
> Priority: Major
> Attachments: registry-bad.png
>
>
> 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)
