[ 
https://issues.apache.org/jira/browse/NIFI-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865267#comment-17865267
 ] 

Leonidas Raghav commented on NIFI-13540:
----------------------------------------

Hi Bryan, thanks for the suggestion. I realised that I had to restart Nifi 
since the initial processor load failed, so after copy pasting the new version 
from the M4 docs (while using Nifi 2.0.0-M3) it worked upon restarting Nifi. 

For future reference for anyone else who faces this issue:
(From the 2.0.0-M4 python developer guide)
"Therefore, it’s important to ensure that the Processor is in a good working 
state before attempting to load it in NiFi. Otherwise, NiFi will need to be 
restarted in order to discover the Processor and load it again."

> TypeError in Python Processor Extension 'WriteHelloWorld' (example from docs) 
> Due to Unexpected Argument 'jvm'
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-13540
>                 URL: https://issues.apache.org/jira/browse/NIFI-13540
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 2.0.0-M3
>         Environment: M1 Max, Mac OS Sonoma
>            Reporter: Leonidas Raghav
>            Priority: Major
>         Attachments: err.log
>
>
> When trying the example Python extension from here
> (https://nifi.apache.org/documentation/nifi-2.0.0-M3/html/python-developer-guide.html),
>  copy-pasted directly into a file called WriteHelloWorld.py in the required 
> directory I get the attached error stating:
> TypeError: FlowFileTransform.__init__() got an unexpected keyword argument 
> 'jvm'
> The attached err.log file has more details of the error. 
> The custom processor WriteHelloWorld does show up in the list and can be 
> dragged onto the canvas, but fails to load due to the error above. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to