You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2023/12/06 17:11:00 UTC

[jira] [Assigned] (NIFI-11789) ExecuteSQL doesn't set fragment.count attribute when Output Batch Size is set

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

Matt Burgess reassigned NIFI-11789:
-----------------------------------

    Assignee:     (was: Matt Burgess)

> ExecuteSQL doesn't set fragment.count attribute when Output Batch Size is set
> -----------------------------------------------------------------------------
>
>                 Key: NIFI-11789
>                 URL: https://issues.apache.org/jira/browse/NIFI-11789
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Tamas Neumer
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Hi,
> I am working with the ExecuteSQL processor and discovered an unexpected behavior. If I specify the attribute "Output Batch Size", I get the fragment.index on the outflowing flowing Flowfiles, but the fragment.count attribute is not set (according to the documentation).
> The behavior I would expect (in line with how merge processors work) is that the attribute fragment.count is just set at the last Flowfile for the batch. This would make it possible to merge all the batches together afterward.
> So my proposal, in short, is that the fragment.count should be set in the last Flowfile of a batch. 
> BR Florian



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