Perhaps the UI could have a placeholder for a missing processor, and the context menu or body could include more details as far as which processor it was looking for.
Sent from my iPhone > On Nov 10, 2015, at 8:30 PM, Chakrader Dewaragatla > <[email protected]> wrote: > > Thank you. I wish this process get simpler in next releases. > > From: Matthew Clarke [[email protected]] > Sent: Tuesday, November 10, 2015 3:58 PM > To: [email protected] > Subject: Re: Nifi service fail to start - Removed custom processor > > It may be easier if possible to add your custom processors back in to the lib > dir, start your NiFi, and then remove them from the canvas. You should them > be able to stay without the custom processor libraries. > >> On Nov 10, 2015 6:23 PM, "Tony Kurc" <[email protected]> wrote: >> And I overlooked one important piece, my approach would be to remove the >> processors you no longer 'installed' >> >>> On Nov 10, 2015 6:13 PM, "Tony Kurc" <[email protected]> wrote: >>> My approach is to modify conf/flow.xml.gz file by hand. There may be bit of >>> a more user friendly approach. >>> >>> gunzip flow.xml.gz >>> vim flow.xml >>> gzip flow.xml >>> >>>> On Tue, Nov 10, 2015 at 6:05 PM, Chakrader Dewaragatla >>>> <[email protected]> wrote: >>>> Hi - We developed few custom processors and built multiple work flows. >>>> Latter, I removed some custom processors (with out clearing the >>>> processors/workflows associated to it on canvas). Now nifi service fail to >>>> start as it try to instatiate the (removed) custom processors. How do we >>>> fix it? >>>> >>>> Thanks, >>>> -Chakri >>>> >>>> >>>> >>>> >>>> >>>> The information contained in this transmission may contain privileged and >>>> confidential information. It is intended only for the use of the person(s) >>>> named above. If you are not the intended recipient, you are hereby >>>> notified that any review, dissemination, distribution or duplication of >>>> this communication is strictly prohibited. If you are not the intended >>>> recipient, please contact the sender by reply email and destroy all copies >>>> of the original message. > > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby notified > that any review, dissemination, distribution or duplication of this > communication is strictly prohibited. If you are not the intended recipient, > please contact the sender by reply email and destroy all copies of the > original message.
