Hello, I have recently posted something relevant to this here but this post is slightly more specific, I'm very sorry for the repetition.
In our NiFi pipelines we have many different versioned groups that do slightly different things. They all have subgroups within that are often exactly the same, and so they are versioned as well and share between parent groups. This means that we generally have two layers of versioning (Versioned groups made up of versioned groups). This used to work almost perfectly (except for some NiFi Registry - Parameter Context intercation funkiness), however since we upgraded from 2.2.0 to 2.6.0 a significant problem has been introduced. In 2.2.0 if I created a new instance of a versioned flow (containing other versioned flows) I would simply click configure, select a parameter context, click "Apply Recursively", and click Apply, which would work exactly as expected. In 2.6.0 if I create a new instance of a versioned flow and follow the same steps I get the message: "server****.***.**:8443 is unable to fulfill this request due to: Cannot set Version Control Info because process group is already under version control". So here are my questions: Is there a fix for this that is not some extremely time consuming workaround? Is it a bug or intended behaviour? If it is a bug then will it be fixed with 2.7.0? If it is intended then... why???? I have spent so far three full work days just switching parameter contexts by hand and it is unbearable. Please help. Thank you, Epameinondas Symeonidis
