You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Kalashnikov (JIRA)" <ji...@apache.org> on 2017/04/03 11:19:41 UTC
[jira] [Assigned] (IGNITE-4509) SQL: query with condition on
affinity columns and without joins and subqueries can be replaced with GET
[ https://issues.apache.org/jira/browse/IGNITE-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Kalashnikov reassigned IGNITE-4509:
------------------------------------------
Assignee: Sergey Kalashnikov
> 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.0
>
>
> 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)