lordgamez commented on code in PR #1770: URL: https://github.com/apache/nifi-minifi-cpp/pull/1770#discussion_r1603707487
########## extensions/python/PYTHON.md: ########## @@ -166,6 +166,10 @@ Due to some differences between the NiFi and MiNiFi C++ processors and implement - MiNiFi C++ only supports expression language with flow file attributes, so only FLOWFILE_ATTRIBUTES expression language scope is supported, otherwise the expression language will not be evaluated. - MiNiFi C++ does not support property dependencies, so the property dependencies will be ignored. If a property depends on another property, the property will not be required. - MiNiFi C++ does not support the use of self.jvm member in Python processors that provides JVM bindings in NiFi, it is set to None in MiNiFi C++. +- Dynamic properties are supported in all Python processors and the dynamic properties defined in the flow configuration are automatically added. There is no need to define getDynamicPropertyDescriptor method in the Python processor. The only caveat is that the description of the dynamic property cannot be custom defined. +- In MiNiFi C++ when the processor is stopped the stop event handling is done in the `notifystop()` processor 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++. Review Comment: Yes, good catch, updated in 6015abfc8d282d8e9f9ef7458de4b4686298d696 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
