[
https://issues.apache.org/jira/browse/NIFI-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750754#comment-17750754
]
Matt Burgess commented on NIFI-11789:
-------------------------------------
Makes sense, I will look at how/if we can set the final FlowFile
fragment.count, an initial glance at the code seems to indicate it might be
tricky as the "last flow file" can be processed at different points in the
code. But if we keep a faithful count of all the flowfiles processed, we should
be able to make that work.
> 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)
