Hi @coelacanth , Its me again from the first post you read that helped you resolve the first issue 🙂 All I can say is welcome to the club. the good news for you is i already went through this process and got it working - on windows as well- so hopefully I can get you going as well and save you some headache and time. Basically Enabling the Python Extension out of the box on windows is not going to work and Im not sure if there was any testing done on windows before releasing this feature. First, you are right about python3 vs python as there is no such file under python windows and it should be changed to python. The second problem is the bin folder as it doesnt get created when the python venv gets deployed to the controller folder first when you enable this feature, or when you add any new python extension processor. It seems under windows it creates a folder called Script where it stores all the python commands (.exe), so all you have to do is basically create the bin folder uder .\work\python\controller then copy whatever is under the "Script" folder to it and restart nifi and hopefully it will work. You only have to do that once for the controller folder but when you add new python processor and the vevn gets created for it under \work\python\extensions\[Custom Processor]\2.0.0-SNAPSHOT\ You have to do the same thing of creating the bin folder and copying whatever in the Script folder to get it working. Actually the steps I do are the following: 1- Create the Custom processor 2- Copy the custom processor to the python extension folder .\python\extensions 3- Run Nifi the first time to create the Venv for the new processor under .\work\python\extensions\[Custom Processor]\2.0.0-SNAPSHOT\ 4- once the venv folder is created, turn nifi OFF because the custom processor is not going to load correctly and its going to keep saying "installing third party components...". 5- Create the bin folder and copy whatever in the script folder to it \work\python\extensions\[Custom Processor]\2.0.0-SNAPSHOT\bin 6- Run nifi again. If everything is setup correctly with the processor and there is no compiler error , it will take few mins to download the dependencies ( depends ho many you have) and then it should work. The Nifi development community needs to fix this bug either internally looking for the script folder aside from the bin folder, or make that configurable in the nifi.properties. Note about out of the box python extensions: You might have problem getting the dependencies downloaded correctly for the ParseDocument extension. You might need to download those dependencies manually to get it to work and here is another trick for you: if you happen to download those dependencies manually you need to create a file "dependency-download.complete" with "True" value inside under the processor path \work\python\extensions\[Custom Processor]\2.0.0-SNAPSHOT\ to let nifi know that its finished downloading the dependencies and remove the error from the processor. @pvillard, this is another issue that needs your attention. I mean to write an article about this but did not have the time. Any way hopefully that is enough info to get you going. let me know if you have any other questions. If you find this is helpful, please accept solution. Thanks
... View more
