You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Fredrick Eisele (Jira)" <ji...@apache.org> on 2024/03/18 19:38:00 UTC
[jira] [Commented] (NIFI-12916) Develop an ExecutePythonScript Processor
[ https://issues.apache.org/jira/browse/NIFI-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828083#comment-17828083 ]
Fredrick Eisele commented on NIFI-12916:
----------------------------------------
Development repository: https://github.com/phreed/nifi-nar-pythonx
> 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)