rondunn opened a new issue, #6345: URL: https://github.com/apache/jmeter/issues/6345
### Expected behavior The following commit has introduced an undesirable change to the JDBC sampler. https://github.com/apache/jmeter/commit/945281cfaa6cca782f0e11f151eb22497d545713 Prior to this change, the "Limit Resultset" value would only apply when reading the result set, reading would stop after 'n' rows. Now, by this change, the sampler calls SetMaxRows() to the limit value. This can then be used by the JDBC client and server to optimise the query, such as by pushing a LIMIT clause into the query plan which can terminate server processing before all results have been generated. I believe this behaviour should be rolled back, as it invalidates a common requirement of database performance testing. ### Actual behavior _No response_ ### Steps to reproduce the problem https://github.com/apache/jmeter/commit/945281cfaa6cca782f0e11f151eb22497d545713 ### JMeter Version 5.6.3 ### Java Version _No response_ ### OS Version _No response_ -- 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: dev-unsubscr...@jmeter.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
