|
Thanks to provide trace level info. Can you indicate if you use some sort of proxy , and if so the version as well ? I suspect that issue occurs at that level.
trace info will confirm it, but if the change of CONJ-1015 is the reason of the issue, disabling option permitPipeline is a workaround for this
|
|
Additional info :
For the very same database it works in a different scenario (a different table/statement) :
create table table2
(
c1 timeStamp(6) not null default CURRENT_TIMESTAMP(6),
c2 timeStamp(6) not null default CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6),
c3 varchar(30) not null default LOWER(SUBSTRING_INDEX(USER(), '@', 1)),
c4 date not null,
c5 char(2) not null,
c6 varchar(255),
primary key (c4, c5)
);
INSERT INTO table2 (c3, c4, c5, c6)
VALUES (?, ?, ?, ?);
So I think we can rule out proxies. Storage engine here is innoDb and not MEMORY. The table do have a primary key. Both table are empty before the insertion. The batch size here is around 600 rows. No decimal(10,6) field in this table
|
|
I provided in attachment a simple plain main java to reproduce the problem
A basic table :
CREATE TABLE mytable
(
c1 bigint not null,
c2 decimal(10,6) not null,
c3 decimal(10,6) not null,
c4 decimal(10,6),
c5 decimal(10,6),
c6 decimal(10,6),
c7 decimal(10,6)
)
A basic Java program :
import java.math.BigDecimal;
import java.sql.Connection;
import java.sql.Driver;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
public class TestMariaDbBatchUpdateBulInsertPipeline {
private static final String[] VALUES =
{"1.1", "2.22", "3.333", "4.4444", "5.55555", "6.666666"}
;
public static void main(String[] args) throws Exception {
if (args.length < 5)
{
System.out.println("\n\nUsage host port database user password keystorePassword\n");
}
DriverManager.registerDriver((Driver) Class.forName("org.mariadb.jdbc.Driver").newInstance());
try (Connection connection = DriverManager.getConnection("jdbc:mariadb://" + args[0]+ ":" + args[1]+ "/" + args[2]+ "?user=" + args[3]+ "&password=" + args[4]+ "&useBulkStmts=true&allowLocalInfile=false&useCompression=true&useServerPrepStmts=true&useSSL=true&trustServerCertificate=true&enabledSslProtocolSuites=TLSv1.3")) {
try (PreparedStatement ps = connection.prepareStatement("INSERT INTO mytable (c1, c2, c3, c4, c5, c6, c7) VALUES (?, ?, ?, ?, ?, ?, ?)")) {
for (long i = 0; i < 200; i++) { // STOP WORKING AT 152 ROWS AND CRASH WITH java.sql.SQLException: (conn=21803) Incorrect arguments to mysqld_stmt_bulk_execute
ps.setLong(1, i);
for (int j = 0; j < 6; j++)
{
ps.setBigDecimal(j + 2, new BigDecimal(VALUES[j]));
}
ps.addBatch();
}
ps.executeBatch();
}
}
}
}
Some conclusion :
Works for small number of rows but stop working at 152 rows and more
Over 152 rows only the first 151 rows are inserted
Works well in all scenario with version 3.0.9
Enabling/Disabling compression don't change the outcome
|
|
Using double works well :
ps.setDouble(j + 2, Double.valueOf(VALUES[j]));
instead of
ps.setBigDecimal(j + 2, new BigDecimal(VALUES[j]));
and I can reach over 100,000 rows inserted. So sounds like the problem is limited to BigDecimal usage
|
calcenginegw-mariadb-bulkinsert-failure.log
test-maria-db-client-bulk-insert-pipeline-bigdecimal.tgz