You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:07 UTC

[jira] [Resolved] (NIFI-8733) PutSQL fragmented transaction issue

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

Pierre Villard resolved NIFI-8733.
----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> PutSQL fragmented transaction issue
> -----------------------------------
>
>                 Key: NIFI-8733
>                 URL: https://issues.apache.org/jira/browse/NIFI-8733
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: NiFi Stateless
>    Affects Versions: 1.12.1
>         Environment: 3 Node Cluster
>            Reporter: ChuaSweeChin
>            Priority: Major
>         Attachments: Screenshot 2021-06-22 at 1.40.37 AM.png, Screenshot 2021-06-22 at 1.48.13 AM.png
>
>
> I am hitting an issue with PutSQL processor which is pretty weird. 
> What happen is, I have a 987 flow files sharing the same attributes [fragment.identifier], [fragment.count] and their respective [fragment.index] all stuck in upstream of PutSQL.
> In PutSQL, I have configured [Support Fragmented Transactions] to TRUE. If I understand correctly, when [Support Fragmented Transactions] is TRUE, PutSQL will wait till all the fragments arrive before executing the transaction, in which in my case, the fragment all arrived however the sql execution did not.
> Only when I restart PutSQL, then all the 987 flow files will get processed successfully right away.
> If I reconfigure [Transaction Timeout] to 5000ms, then the 987 flow files will flow to failure relationship after 5000ms. This I assume PutSQL is unable to detect that all the fragments has arrived upstream and push it to failure.
> The other thing I tried is that if I reconfigure [Support Fragmented Transactions] to FALSE, then the flow files will all get processed successfully right away.
> I am not entirely sure why PutSQL is behaving this way for fragmented transaction I was hoping someone could help me out on this. 



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