[jira] [Updated] (MINIFICPP-1990) Transferring FlowFiles in Python Processors

["Gábor Gyimesi (Jira)" <ji...@apache.org>]

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

Gábor Gyimesi updated MINIFICPP-1990:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Transferring FlowFiles in Python Processors
> -------------------------------------------
>
>                 Key: MINIFICPP-1990
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1990
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Kondakov Artem
>            Assignee: Gábor Gyimesi
>            Priority: Major
>             Fix For: 0.14.0
>
>         Attachments: image-2022-11-23-20-03-09-400.png, image-2022-11-23-20-03-53-653.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Hello.
> There is a problem with the processing of flow-files in python processors, which are connected using the setting
> nifi.python.processor.dir=./minifi-python/
> If you need to split one file into several, then you have to create new files in the Python processor and be sure to transfer the original one to REL_FAILURE.
> Otherwise, if I do not pass the original file to REL_FAILURE, then the processing result is rolled back and nothing happens
> It seems to me that it is necessary to make it possible for Python processors to add various relations, and not just REL_FAILURE REL_SUCCESS.
> Or add an additional possible relationship REL_ORIGIN to which you can pass the original file
> That. if you look at the metrics for these processors, you see TransferredToFaillure > 0, although the processors processed without errors
> Another additional possibility is to add the session.remove (flowfile ) method (as it is done for example in the processor ExecuteSQL). Then it will be possible to exclude incoming files from further processing
> !image-2022-11-23-20-03-53-653.png!
>  



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