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/07/25 02:46:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17746735#comment-17746735 ]
Matt Burgess commented on NIFI-11789:
-------------------------------------
I'm assuming when you mean "merge all batches together", you mean merge all FlowFiles from a single batch together? Or are you looking to set the final count on the final FlowFile even if Output Batch Size is set?
> 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
> Assignee: Matt Burgess
> Priority: Minor
> Fix For: 1.latest, 2.latest
>
>
> 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)