Kevin -

(sorry for the delay, still waiting for someone from the DevOps team to pull that log file)

We are currently using Registry version 0.2.0.

In our setup we have DEV, QA, and PROD Nifi instances all pointed to the same instance of the registry.

The sequence of steps I used was:

1. Finish making changes to the Process Group in DEV.
2. Right click -> Version - > Commit local changes
3. Wait for check mark to turn green in the bread crumbs at the bottom of the screen.
4. Open QA Nifi interface
5. Navigate to the Process Group in question and open it
6. Right click -> Version - > Change Version
7. Select the new version I saved from dev

This particular change version is number 32, and I've only had one other issue when moving updates.

Getting a new instance of Nifi running 1.8.0 up and running to test with might be possible, but it's a request that has to go through infrastructure to get a VM spun up, and then devops to get the software installed, so it's unfortunately not something that I can do quickly.
Russ Weiher
Data Engineer
Progenity, Inc.
-----Original Message-----
From: Kevin Doran [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 10, 2019 11:16 AM
Subject: Re: Java exception when attempting to update version from registry

Sorry, forgot to add -- can you include the full stack trace for the IllegalStateException as well? It should be in the nifi-app.log file.

On January 10, 2019 at 11:13:33, Kevin Doran ([EMAIL PROTECTED]) wrote:
IMPORTANT: This email (and any attachments) is intended for the use of only the person or entity to which it is addressed, and may contain information that is privileged and confidential. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. Unauthorized redisclosure or failure to maintain confidentiality may subject you to federal and state penalties. If you are not the intended recipient, please immediately notify us by return email, and delete this message from your computer.