hansva opened a new issue, #9248: URL: https://github.com/apache/hop/issues/9248
### Apache Hop version? 2.20.0 ### Java version? 21 ### Operating system macOS ### What happened? **Description** With batch updates and an error hop on a database without row savepoints (SQL Server, Oracle), the row sent to the error hop is the row where the batch was flushed, not the row that failed. Update doesn't buffer the batch or read `BatchUpdateException.getUpdateCounts()` the way Table Output and Synchronize after merge do. The exception comes up on the row that triggered the flush, and that's the row that ends up on the error hop. **To reproduce** 1. Use Update with batch updates on, commit size 100, and an error hop, against SQL Server or Oracle. 2. Make rows 97 and 194 fail. **Expected:** rows 97 and 194 go to the error hop. **Actual:** rows 100 and 200 go to the error hop. The real failing rows aren't reported, and rows that succeeded are flagged as errors. ### Issue Priority Priority: 2 ### Issue Component Component: Database -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
