You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/28 11:38:00 UTC
[jira] [Updated] (IGNITE-11499) SQL: DML should not use batches by
default
[ https://issues.apache.org/jira/browse/IGNITE-11499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-11499:
-------------------------------------
Description:
Currently DML apply updates in batches equal to {{SqlFieldsQuery.pageSize}}. This is prone to deadlocks. Instead, we should apply updates one-by-one by default. Proposal:
# Introduce {{SqlFieldsQuery.updateBatchSize}} property, set it to {{1}} by default
# Print a warning about deadlock to log if it is greater than 1
# Add it to JDBC and ODBC drivers
# Add it to other languages
was:
Currently DML apply updates in batches equal to {{SqlFieldsQuery.pageSize}}. This is prone to deadlocks. Instead, we should apply updates one-by-one by default. Proposal:
# Introduce {{SqlFieldsQuery.updateBatchSize}} property, set it to {{1}} by default
# Print a warning about deadlock to log if it is greater than 1
# Add it to JDBC and ODBC drivers
> SQL: DML should not use batches by default
> ------------------------------------------
>
> Key: IGNITE-11499
> URL: https://issues.apache.org/jira/browse/IGNITE-11499
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.8
>
>
> Currently DML apply updates in batches equal to {{SqlFieldsQuery.pageSize}}. This is prone to deadlocks. Instead, we should apply updates one-by-one by default. Proposal:
> # Introduce {{SqlFieldsQuery.updateBatchSize}} property, set it to {{1}} by default
> # Print a warning about deadlock to log if it is greater than 1
> # Add it to JDBC and ODBC drivers
> # Add it to other languages
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)