[
https://issues.apache.org/jira/browse/IGNITE-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133309#comment-16133309
]
ASF GitHub Bot commented on IGNITE-6024:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/2488
IGNITE-6024: support for server-side dml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6024
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2488.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2488
----
commit 7b3af51a3d6ec538a55c8b0172205a38b87f4e22
Author: skalashnikov <[email protected]>
Date: 2017-08-18T17:13:21Z
IGNITE-6024: support for server-side dml
----
> SQL: execute DML statements on the server when possible
> -------------------------------------------------------
>
> Key: IGNITE-6024
> URL: https://issues.apache.org/jira/browse/IGNITE-6024
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.1
> Reporter: Vladimir Ozerov
> Assignee: Sergey Kalashnikov
> Labels: performance
> Fix For: 2.2
>
>
> Currently we execute DML statements as follows:
> 1) Get query result set to the client
> 2) Construct entry processors and send them to servers in batches
> This approach is inefficient as it causes a lot of unnecessary network
> communication Instead, we should execute DML statements directly on server
> nodes when it is possible.
> Implementation considerations:
> 1) Determine set of queries which could be processed in this way. E.g.,
> {{LIMIT/OFFSET}}, {{GROUP BY}}, {{ORDER BY}}, {{DISTINCT}}, etc. are out of
> question - they must go through the client anyway. Probably
> {{skipMergeTable}} flag is a good starting point (good, not precise!)
> 2) Send request to every server and execute local DML right there
> 3) No failover support at the moment - throw "partial update" exception if
> topology is unstable
> 4) Handle partition reservation carefully
> 5) Transactions: we still have single coordinator - this is a client. When
> MVCC and TX SQL is ready, client will assign proper counters to server
> requests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
