That sounds like a good plan, sorry it has been so challenging to get setup.
I'm hoping that the old flow will still start up despite the API changes that are affecting the scripting processor, but I'm actually not sure when the errors would end up being detected (start up vs. runtime of processor). Let us know. -Bryan On Fri, Sep 9, 2016 at 8:15 AM, bmichaud <ben_mich...@optum.com> wrote: > bmichaud wrote > > > > Bryan Bende wrote > >> Can you explain a little more about what you mean by "scripts containing > >> compile errors"? Are you talking about ExecuteScript processors? > > > > bmichaud wrote > >> Yes, they are errors in the Groovy code inserted into ExecuteScript > >> Processor. Mostly, the error lies in the change from "ProcessLog" to > >> "ComponentLog". My question is can the security migration work and can I > >> use the NiFi GUI when such errors exist in the flow.xml.gz file? > > I beg your pardon. It was not ExecuteScript, it was a different processor > whose name I cannot remember at the moment, and I cannot see it right now, > that a colleague of mine created. This processor allows you to put an > entire > processor extension (a full Processor class) into it. > > > > > > > -- > View this message in context: http://apache-nifi-developer- > list.39713.n7.nabble.com/Questions-regarding-security- > set-up-in-NiFi-1-0-0-tp13288p13301.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
