Processor Python Creation

[Luis Carmona <lu...@openpartner.cl>]

Hi guys,

according to what I understand from the documentation, every time I 
create a python processor and manage to add it to nifi it should be 
started from a new instance of the selected python interpreter. To be 
more accurate, it should be started from it's own new virtual 
environment - created under .../work/..., and this python should start 
the python module as a new process.

But there are a couple of things I'm doing wrong or I am not 
understanding well from the documentation, because:

1. Everytime I modify the python code of a processor and stop it, all 
the dependencies are re-installed. Doesn't matter if I just changed code 
or added any new library. Is that ok ?

2. When I stop and/or disable the custom processor, the os process 
doesn't die, it stays running or in some state. The sequence I think 
happens is watching Linux htop:

- Java starts a controller (python)

- The custom python component starts the python controller as well ¿?

I am going nuts with some strange behavior with this cause it is not 
easy to understand if the process hung up, or I have a bug, or the 
processor hasn't actually been reloaded and restarted.


Is there any document about the mechanics of this I can read ?


Thanks in advance


LC