I would also check the poll period. E.g. give it 40 secs or more to detect
new versions in the registry, it's not real time.
Andrew
On Thu, Jul 19, 2018, 6:35 AM Mike Thomsen wrote:
> Thanks, Kevin. If I get a chance I'll try it out again because it appeared
> to be the case that after the
Thanks, Kevin. If I get a chance I'll try it out again because it appeared
to be the case that after the definition changed to B:v2 that A did not
show any sign it was changed. Could just be me misremembering it because it
was late when we tried it.
On Wed, Jul 18, 2018 at 9:50 PM Kevin Doran
Hi Mike,
Yes, this is expected behavior.
Let's say I have a PG A that has a nested versioned PG B, both are at
version 1. Because PG B is versioned, the full definition of PG A does not
extend down into PG B, it stops at a reference to "PG B:v1". Because PG B
is versioned independently, a
We have 0.2 hooked up to a NiFi instance that has nested PGs. All PGs are
versioned. When one of the inner ones has local changes, the out of sync
icon doesn't appear on the parent PGs. Is that expected behavior? No one
really minds it, but I didn't have an answer as to whether we stumbled onto
a
