You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/09/26 10:40:00 UTC
[jira] [Resolved] (IGNITE-16085) Calcite engine. Index can't be used with IS NULL condition
[ https://issues.apache.org/jira/browse/IGNITE-16085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov resolved IGNITE-16085.
----------------------------------------
Fix Version/s: 2.15
Release Note: SQL Calcite: Added support for index scans by IS NULL/IS NOT NULL conditions
Resolution: Fixed
Resolved by IGNITE-15425
> Calcite engine. Index can't be used with IS NULL condition
> ----------------------------------------------------------
>
> Key: IGNITE-16085
> URL: https://issues.apache.org/jira/browse/IGNITE-16085
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite2-required, calcite3-required
> Fix For: 2.15
>
>
> Currently, we support only {{EQUALS}}, {{LESS_THAN}}, {{GREATER_THAN}}, {{GREATER_THAN_OR_EQUAL}}, {{LESS_THAN_OR_EQUAL}} conditions for index scans. Our indexes also can be scanned for null values by design, but full table scan now performed for {{IS NULL}} condition on indexed fields.
> Perhaps {{IS NOT NULL}}, {{IS TRUE}}, {{IS FALSE}}, {{IS NOT TRUE}}, {{IS NOT FALSE}} also can be used in index scan.
> Also, {{SortedSegmentedIndex#find}} method have {{lowerIncl}} and {{upperIncl}} parameters now, perhaps we can set they to {{false}} for {{LESS_THAN}} and {{GREATER_THAN}} operators to more effective index scans.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)