james94 commented on code in PR #1853: URL: https://github.com/apache/nifi-minifi-cpp/pull/1853#discussion_r1708049608
########## extensions/python/PYTHON.md: ########## @@ -172,10 +172,11 @@ Due to some differences between the NiFi and MiNiFi C++ processors and implement - In MiNiFi C++ when the processor is stopped the stop event handling is done in the `notifyStop()` method which does not have the context available. Due to this the `def onStopped(self, context)` cannot be called in NiFi Python processors, so the `onStopped` method is not supported in MiNiFi C++. - The interface of the `ProcessContext` class is a bit more limited in MiNiFi C++ compared to NiFi. The available methods in `ProcessContext` are `getProperty`, `getStateManager`, `getName` and `getProperties`. - Success relationship is always present in all Python processors even if custom relationships are defined in the Python processor with the `getRelationships` method. +- MiNiFi C++ uses a single embedded Python interpreter for all Python processors, so the Python processors share the same Python interpreter. This means that the Python processors cannot have different Python versions or use different Python packages. The Python packages are installed on the system or in a single virtualenv that is shared by all Python processors. Review Comment: In the case of NiFi 2.0, I believe that each new python processor uses its own virtual environment and probably its own python interpreter per processor. Will this be eventually the case for MiNiFi C++'s python processors? If we use NiFi Native Python Processors in MiNiFi C++, will this behavior with python interpreter happen here in MiNiFi C++? @lordgamez @szaszm -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
