[
https://issues.apache.org/jira/browse/IGNITE-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998818#comment-15998818
]
ASF GitHub Bot commented on IGNITE-4509:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1916
IGNITE-4509: send unicast sql request when partition can be deduced f…
…rom the query
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4509
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1916.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 #1916
----
commit 4a1768d28550286d69134ff62ee29994a0faa188
Author: skalashnikov <skalashni...@gridgain.com>
Date: 2017-05-04T11:42:40Z
IGNITE-4509: send unicast sql request when partition can be deduced from
the query
----
> SQL: query with condition on affinity columns and without joins and
> subqueries can be replaced with GET
> -------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-4509
> URL: https://issues.apache.org/jira/browse/IGNITE-4509
> Project: Ignite
> Issue Type: Task
> Components: SQL
> Affects Versions: 1.8
> Reporter: Vladimir Ozerov
> Assignee: Sergey Kalashnikov
> Labels: performance, sql
> Fix For: 2.1
>
>
> Simple SQL queries usually demonstrate negative scalability when more nodes
> are added.
> Consider the following query:
> {code}
> SELECT * FROM Person p
> WHERE p.id = ?
> {code}
> If {{Person.id}} is affinity field, then query can be replaced with plain
> {{IgniteCache.get}} or some specialized version of GET, which will return
> only desired fields. This optimization will guarantee smooth scale with any
> number of nodes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
