Pavel Pereslegin created IGNITE-27117:
-----------------------------------------
Summary: Sql. Investigate flaky failures of
ItJdbcBatchSelfTest.testBatchException and testBatchParseException
Key: IGNITE-27117
URL: https://issues.apache.org/jira/browse/IGNITE-27117
Project: Ignite
Issue Type: Bug
Components: jdbc ai3
Reporter: Pavel Pereslegin
With the new implementation of {{Statement.executeBatch}}, some old tests have
become unstable ({{testBatchException}} and {{testBatchParseException}}).
Example:
https://ci.ignite.apache.org/viewLog.html?buildId=9667373&buildTypeId=ApacheIgnite3x_Test_RunIntegrationTests&fromSakuraUI=true
{noformat}
java.lang.AssertionError: Error message
Expected: a string containing "Invalid SQL statement type"
but: was "org.apache.ignite.sql.SqlException: IGN-SQL-6 The query was
cancelled while executing. TraceId:cb878371"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at
org.apache.ignite.jdbc.util.JdbcTestUtils.assertThrowsSqlException(JdbcTestUtils.java:72)
at
org.apache.ignite.jdbc.ItJdbcBatchSelfTest.testBatchException(ItJdbcBatchSelfTest.java:311)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
{noformat}
There is an assumption that the issue is somewhere inside multistatement
handler.
This is only related to Statement.executeBatch (not
PreparedStatement.executeBatch).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
