[
https://issues.apache.org/jira/browse/IGNITE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525197#comment-16525197
]
Taras Ledkov edited comment on IGNITE-4150 at 6/27/18 3:54 PM:
---------------------------------------------------------------
[~vozerov], I've fixed failures at the parser, collocation model building and
{{RECOMPILE_ALWAYS}} option
The SQL tests are OK. Please take a look.
A little comment about the option {{RECOMPILE_ALWAYS}}.
We set {{RECOMPILE_ALWAYS=1}} at the master and used H2 v1.4.195
In this version {{Boolean.parseBoolean}} is used to parse base settings value.
So, we always use H2 with disabled {{RECOMPILE_ALWAYS}}.
was (Author: tledkov-gridgain):
[~vozerov], I've fixed failures at the parser, collocation model building and
{{RECOMPILE_ALWAYS}} option
The SQL tests are OK. Please take a look.
> B-Tree index cannot be used efficiently with IN clause.
> -------------------------------------------------------
>
> Key: IGNITE-4150
> URL: https://issues.apache.org/jira/browse/IGNITE-4150
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 1.7
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Labels: performance
> Fix For: 2.7
>
>
> Consider the following query:
> {code}
> SELECT * FROM table
> WHERE a = ? AND b IN (?, ?)
> {code}
> If there is an index {{(a, b)}}, it will not be used properly: only column
> {{a}} will be used. This will leads to multiple unnecessary comparisons.
> Most obvious way to fix that - use temporary table and {{JOIN}}. However,
> this approach doesn't work well when there are multiple {{IN}}'s.
> Proper solution would be to hack deeper into H2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
