You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gábor Gyimesi (Jira)" <ji...@apache.org> on 2025/09/29 12:45:00 UTC

[jira] [Updated] (MINIFICPP-2640) Remove explicit use of ExecutePythonProcessor

     [ https://issues.apache.org/jira/browse/MINIFICPP-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gábor Gyimesi updated MINIFICPP-2640:
-------------------------------------
    Summary: Remove explicit use of ExecutePythonProcessor  (was: Remove explicit usa of ExecutePythonProcessor)

> Remove explicit use of ExecutePythonProcessor
> ---------------------------------------------
>
>                 Key: MINIFICPP-2640
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-2640
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Task
>            Reporter: Gábor Gyimesi
>            Assignee: Gábor Gyimesi
>            Priority: Major
>             Fix For: 1.0.0
>
>
> ExecutePythonProcessor is meant to be used for running native python processors for both minifi c++ style and nifi style python processors. These native python processors are read from the directory defined in the nifi.python.processor.dir property. In previous releases it was possible to use ExecutePythonProcessor explicitly and setting its properties to define the path of the python processor and the used module paths. This usage should be removed in favor of the automatic python processor parsing and using the created virtual environment for dependency modules. Removing this option also makes the ExecutePythonProcessor code cleaner and simpler.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)