Tim, Just wanted to provide a few more details. Prior to 1.2.0 the flow and templates did not contain any details about the NAR (bundle) it was packaged in. In 1.2.0, since your template did not contain any bundle details NiFi attempted to find a compatible Processor (matched by class name only). If the instance detects that more than one Processor exists with that class name you will receive the error you described.
Re-exporting the template in 1.2.0 will include the relevant bundle details for future use. Hope this helps Matt On Thu, May 11, 2017 at 7:52 PM, Andy LoPresto <[email protected]> wrote: > Hi Tim. > > What processor has multiple versions and which is the desired target? As > your 1.2.0 installation is a clean install, I would actually recommend just > exporting the complete flow.xml.gz file from your existing 1.1.2 instance > and placing it in the $NIFI_HOME/conf directory for the 1.2.0 instance. > > Bryan Bende also wrote a good article describing the feature and some of > the background if you haven’t seen it yet [1]. > > [1] http://bryanbende.com/development/2017/05/10/apache- > nifi-1-2-0-component-versioning > > > Andy LoPresto > [email protected] > *[email protected] <[email protected]>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On May 11, 2017, at 4:47 PM, Tim Zimmerman <[email protected]> wrote: > > First thanks for the 1.2.0 release. There are a few things I have been > looking forward to (wait/notify). > > Now, I have a question. I was running 1.1.2 locally and experimenting with > a few ideas. After creating a template and exporting one of those ideas, > I unpacked 1.2.0 and started it up. > > I am able to import the template fine but when I try to place it on the > canvas I get dialog that there is more than one version of the processor on > the path and the template does not appear. > > I understand this is due to the new versioning and I thought maybe if I > just hacked in the <bundle> element I could get this template working but I > did that and tried again but it still does not seem to be working. > > How should I be migrating 1.1.2 work into 1.2.0? > > >
