[GitHub] [ignite-3] lowka commented on pull request #2196: IGNITE-19615: Index is not used while performing SELECT over an indexed column.

["lowka (via GitHub)" <gi...@apache.org>]

lowka commented on PR #2196:
URL: https://github.com/apache/ignite-3/pull/2196#issuecomment-1604399991

   > After this patch an index is used indeed. But resulting plan is rather invalid. For a query like `SELECT val FROM my WHERE id = 100500`, where `id` is of type TINYINT, I've got following plan:
   > 
   > ```
   > IgniteExchange<...>
   >   IgniteIndexScan(<...>, searchBounds=[[ExactBounds [bound=CAST(100500):TINYINT NOT NULL]]], filters=[=(CAST($t0):INTEGER NOT NULL, 100500)]<...>
   > ```
   > 
   > this results in RuntimeException, since 100500 is out of range of TINYINT
   @korlov42 
   I going to look into it. I looked at the result of `IgniteSqlValidator` and it add `INTEGER` casts to both id and literal (this is expected). But somehow the bounds are still use `TINYINT`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org