I tried both along with nifi restart.

it kinda works now. But this is CRAZY. If someone can explain this, I would
give a hug :)

My steps:

1. Drop new InvokeScriptedProcessor on canvas. Open properties and point it
to my groovy file on NFS. Pick Groovy as a lang. Hit Apply
2. Go back in the processor properties to populate my custom properties.
Hit apply
--> Error bulletin popup - cannot validate bla bla

3. Open properties again. change path to groovy script to 1234. Apply
>> obviously error message that script does not exist

4. Open properties again and change path BACK to NFS path from step 1. This
is exactly the same file/path. Hit Apply
>> All works now, no errors

After NiFi restart processor still works, no errors. But if I start over
from step 1, I have to repeat all steps again.

On Tue, May 22, 2018 at 4:22 PM, Shawn Weeks <[email protected]>
wrote:

> Were you disabling the processor or just stopping it? I've found with the
> scripted processors they will get in an odd state and that's the only way
> to reset it.
>
>
> Shawn
> ------------------------------
> *From:* Boris Tyukin <[email protected]>
> *Sent:* Tuesday, May 22, 2018 3:07:36 PM
> *To:* [email protected]
> *Subject:* Re: InvokeScriptedProcessor from a shared folder
>
> well it works now...after I recreated processor 3 times and was changing
> parameters back and forth and now that error is gone.
>
> we did not change permissions on nfs or file so not sure why nifi did not
> like it at first.
>
> On Tue, May 22, 2018 at 3:32 PM, Boris Tyukin <[email protected]>
> wrote:
>
> Hello,
>
> I created a custom groovy processor and saved it in a file. That file was
> placed on NFS share and I pointed NiFi's InvokeScriptedProcessor to it.
>
> When I started a processor, I got a weird error that it failed custom
> validation.
>
> If I copy that file out of NFS to a local directory, it works fine.
>
> It seems that NiFi is trying to obtain a file lock or something that NFS
> does not support.
>
> Can someone shed some light on this? We were hoping to keep scripted
> processors on NFS so they accessible from all the nodes and also deployed
> to a single place.
>
> Thanks,
> Boris
>
>
>

Reply via email to