[
https://issues.apache.org/jira/browse/NIFI-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fredrick Eisele updated NIFI-12916:
-----------------------------------
Description:
Given the ability to create python processors in NiFi 2, and the presence of
ExecuteGroovyScript, development of an ExecutePythonScript processor seems
logical.
That said there will be differences due to differences between on the NiFi
Python and JVM support.
The first step is to outline what capabilities are or may be possible.
"The new native Python support in NiFi 2.0 provides a more streamlined API for
Processor implementation, as opposed to the full set of capabilities that the
Java Processor API provides.
This enables simplified Processor implementation, and streamlined communication
between Java and Python processes.
For that reason, a generic ExecutePythonScript would not provide all of the
same options as the generalized ExecuteGroovyScript."
Ref:
*
[https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-processors/src/main/java/org/apache/nifi/processors/groovyx]
*
[https://nifi.apache.org/documentation/nifi-2.0.0-M2/html/python-developer-guide.html]
was:
Given the ability to create python processors in NiFi 2, and the presence of
ExecuteGroovyScript, development of an ExecutePythonScript processor seems
logical.
That said there will be differences due to differences between on the NiFi
Python and JVM support.
The first step is to outline what capabilities are or may be possible.
"The new native Python support in NiFi 2.0 provides a more streamlined API for
Processor implementation, as opposed to the full set of capabilities that the
Java Processor API provides.
This enables simplified Processor implementation, and streamlined communication
between Java and Python processes.
For that reason, a generic {{ExecutePythonScript}} would not provide all of the
same options as the generalized {{{}ExecuteGroovyScript{}}}."
> Develop an ExecutePythonScript Processor
> ----------------------------------------
>
> Key: NIFI-12916
> URL: https://issues.apache.org/jira/browse/NIFI-12916
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 2.0.0-M2
> Reporter: Fredrick Eisele
> Priority: Major
> Fix For: 2.0.0-M3
>
>
> Given the ability to create python processors in NiFi 2, and the presence of
> ExecuteGroovyScript, development of an ExecutePythonScript processor seems
> logical.
> That said there will be differences due to differences between on the NiFi
> Python and JVM support.
> The first step is to outline what capabilities are or may be possible.
> "The new native Python support in NiFi 2.0 provides a more streamlined API
> for Processor implementation, as opposed to the full set of capabilities that
> the Java Processor API provides.
> This enables simplified Processor implementation, and streamlined
> communication between Java and Python processes.
> For that reason, a generic ExecutePythonScript would not provide all of the
> same options as the generalized ExecuteGroovyScript."
> Ref:
> *
> [https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-processors/src/main/java/org/apache/nifi/processors/groovyx]
> *
> [https://nifi.apache.org/documentation/nifi-2.0.0-M2/html/python-developer-guide.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
