Bryan,
Wanted to update you. Spoke with Hortonworks and they informed me the
version definitions included in the HDF 3.3.x versions used NiFi Registry
0.3.0 because 0.3.0 was supposed to go in those releases. Unfortunately it
was discovered that NiFi Registry was pointed at the wrong repo and
Bryan,
Thanks for the update. I will reach out to Hortonworks to see what could be
happening. I'll update this thread with what I find.
-Chad
On Tue, Feb 19, 2019 at 3:49 PM Bryan Bende wrote:
> Chad,
>
> I suspect it may be an issue with the version of NiFi registry in the
> vendor
Chad,
I suspect it may be an issue with the version of NiFi registry in the
vendor distribution.
As far as I can tell, it is working correctly on apache releases of
NiFi 1.8.0/1.9.0-RC2 and registry 0.3.0.
-Bryan
On Tue, Feb 19, 2019 at 3:27 PM Chad Woodhead wrote:
>
> Bryan,
>
> I also just
Bryan,
I also just tested with a new flow not in version control with NiFi
Registry and then started version control with it, and same behavior on my
side. No load balance connection properties in the snapshot.
Thanks,
Chad
On Tue, Feb 19, 2019 at 3:21 PM Chad Woodhead
wrote:
> Bryan,
>
> No
Bryan,
No the snapshot in my git repo (we use GitFlowPersistenceProvider) does not
have the load balance connection properties. If I create a template of the
same PG on NiFi, I do see the load balance connection properties in the
xml. So for some reason the load balance connection properties are
Chad,
Using the 1.9.0-RC2 build of NiFi and the 0.3.0 release of registry, I
haven't been able to reproduce the issue.
I don't know of anything that would have fixed the issue between 1.8.0
and 1.9.0, so I'm not sure what you are running into.
Can you look in your registry flow_storage
I am running NiFi 1.8.0 and NiFi Registry 0.3.0. I have noticed load
balance strategies on queues aren't coming through versioned flows in NiFi
Registry. Here are the steps I am performing:
1. Have existing flow running on latest flow version in Dev and Cert (flow
has already been developed and
