[jira] [Created] (IGNITE-25768) Sql. Invalid search boundaries are generated when accessing the index if the key is out of range

[Pavel Pereslegin (Jira)]

Pavel Pereslegin created IGNITE-25768:
-----------------------------------------

             Summary: Sql. Invalid search boundaries are generated when 
accessing the index if the key is out of range
                 Key: IGNITE-25768
                 URL: https://issues.apache.org/jira/browse/IGNITE-25768
             Project: Ignite
          Issue Type: Bug
          Components: sql, sql ai3
            Reporter: Pavel Pereslegin


Consider the following:

{code:sql}
CREATE TABLE t (id TINYINT PRIMARY KEY, val TINYINT);
CREATE INDEX t_val_idx ON t (val);
{code}

PLAN TableScan vs IndexScan
{code:sql}
sql("EXPLAIN SELECT /*+ NO_INDEX */ val FROM t WHERE val = ?", 100500)
sql("EXPLAIN SELECT /*+ FORCE_INDEX(t_val_idx) */ val FROM t WHERE val = ?", 
100500)
{code}

{noformat}
  TableScan
      table: PUBLIC.T
      predicate: =(CAST(VAL):INTEGER, ?0)
      fieldNames: [VAL]
      est: (rows=1)

  IndexScan
      table: PUBLIC.T
      index: T_VAL_IDX
      type: SORTED
      predicate: =(CAST(VAL):INTEGER, ?0)
      searchBounds: [ExactBounds [bound=CAST(?0):TINYINT]]
      fieldNames: [VAL]
      collation: [VAL ASC]
      est: (rows=1)
{noformat}

As a result: TableScan returns no rows, but IndexScan fails with:

{noformat}
Caused by: 
org.apache.ignite.internal.sql.engine.exec.RemoteFragmentExecutionException: 
IGN-SQL-7 TINYINT out of range TraceId:e329e323
        at 
org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl.onMessage(ExecutionServiceImpl.java:575)
        ... 7 more
{noformat}




--
This message was sent by Atlassian Jira
(v8.20.10#820010)