[
https://issues.apache.org/jira/browse/IGNITE-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-17889:
---------------------------------------
Labels: calcite calcite3-required (was: calcite calcite2-required
calcite3-required)
> Calcite engine. Avoid full index scans in case of null dynamic parameter
> ------------------------------------------------------------------------
>
> Key: IGNITE-17889
> URL: https://issues.apache.org/jira/browse/IGNITE-17889
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, calcite3-required
> Fix For: 2.15
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently, queries like:
> {code:java}
> SELECT * FROM tbl WHERE a >= ?
> {code}
> Should return no rows if dynamic parameter is null, but can be downgraded to
> full index scan in case table have index on column {{a}} (ASCENDING order,
> NULLS FIRST).
> We should somehow analyse nulls in search bounds and return empty rows
> iterator for regular field conditions (`=`, `<`, '>`, etc). But also nulls
> should be processed as is in search bounds for conditions like `IS NULL`, `IS
> NOT NULL`, `IS NOT DISTINCT FROM` (the last one not supported currently).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
