Yury Gerzhedovich created IGNITE-18890:
------------------------------------------
Summary: Sql. Avoid full index scans in case of null dynamic
parameter
Key: IGNITE-18890
URL: https://issues.apache.org/jira/browse/IGNITE-18890
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Yury Gerzhedovich
The ticket is a copy of IGNITE-17889 to port it from AI2 to AI3.
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)
