ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taras Ledkov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-11499) SQL: DML should not use batches by default
Date Thu, 11 Apr 2019 08:55:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815218#comment-16815218
] 

Taras Ledkov edited comment on IGNITE-11499 at 4/11/19 8:54 AM:
----------------------------------------------------------------

[~vozerov],
About fast update: this is a special mode to update / delete only one specified key.
Looks like the {{updateBatchSize}} is not applicable for fast update mode.
 please take a look.


was (Author: tledkov-gridgain):
[~vozerov], please take a look.

> 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
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)

Mime
View raw message