[ https://issues.apache.org/jira/browse/IGNITE-17889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621505#comment-17621505 ]
Ignite TC Bot commented on IGNITE-17889: ---------------------------------------- {panel:title=Branch: [pull/10338/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} {panel:title=Branch: [pull/10338/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1} {color:#00008b}Calcite SQL{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=6844840]] * {color:#013220}IgniteCalciteTestSuite: IndexScanlIntegrationTest.testNullsInCNLJSearchRow - PASSED{color} {panel} [TeamCity *--> Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6844483&buildTypeId=IgniteTests24Java8_RunAll] > 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, calcite2-required, calcite3-required > Time Spent: 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)