[
https://issues.apache.org/jira/browse/NIFI-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750645#comment-17750645
]
Tamas Neumer commented on NIFI-11789:
-------------------------------------
HI Matt,
"merge all batches together" for me means the following:
Imagine the situation that one flowfile is coming to the ExecuteSQL processor.
Let's assume there 8 records to fetch and the batch size is set to 1.
This would result in 3 batches of size 3, 3 and 2 flowfiles.
What i want to achieve is to merge all 8 flowfiles back into one.
So i would number them 1-8 and set the fragment.count to 8
BR
> 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)
