markap14 commented on code in PR #7003:
URL: https://github.com/apache/nifi/pull/7003#discussion_r1142669010


##########
nifi-docs/src/main/asciidoc/administration-guide.adoc:
##########
@@ -231,6 +232,38 @@ The `name` attribute must start with `deprecation`, 
followed by the component cl
 <logger name="deprecation.org.apache.nifi.processors.ListenLegacyProtocol" 
level="OFF" />
 ----
 
+[[python_configuration]]
+== Python Configuration
+
+NiFi if a Java-based application. However, in the 2.0 release, support was 
introduces for a Python-based Processor API. This capability is still
+considered to be in "Beta" mode and should not be used in production. By 
default, support for Python-based Processors is disabled. In order to enable it,
+Python 3.9+ must be installed on the NiFi node.
+
+The following properties may be used to configure the Python 3 installation 
and process management. These properties are all located under the
+"Python Extensions" heading in the _nifi.properties_ file:
+
+[options="header,footer"]
+|==================================================================================================================================================
+| Property Name | Default Value | Description
+| nifi.python.command | python3 | The command used to launch Python. By 
default, this property is set to "python3" but commented out. In order to 
enable Python-based Processors,
+uncomment this line and set it to the command that should be used to invoke 
Python 3.
+| nifi.python.framework.source.directory | ./python/framework | The directory 
that contains the Python framework for communicating between the Python and 
Java processes.
+| nifi.python.extensions.source.directory.default | ./python/extensions | The 
directory that NiFi should look in to find Python-based Processors. Note that 
this property is supplied

Review Comment:
   The API directory is expected to be a sibling of the framework directory. 
Will note this in the documentation.



-- 
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]

Reply via email to