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 2017/06/01 13:42:04 UTC
[jira] [Commented] (IGNITE-4509) SQL: query with condition on
affinity columns and without joins and subqueries should go to affinity
node only
[ https://issues.apache.org/jira/browse/IGNITE-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032996#comment-16032996 ]
Vladimir Ozerov commented on IGNITE-4509:
-----------------------------------------
[~skalashnikov], my comments:
1) {{IgniteSqlRoutingTest}} is not included into test suite
2) {{IgniteSqlRoutingTest}} - please avoid abbreviations in method names.
3) Need to rerun SQL tests as there are some conflicts with master.
> SQL: query with condition on affinity columns and without joins and subqueries should go to affinity node only
> --------------------------------------------------------------------------------------------------------------
>
> 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: important, 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)