[ 
https://issues.apache.org/jira/browse/IGNITE-26029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Iurii Gerzhedovich reassigned IGNITE-26029:
-------------------------------------------

    Assignee: Andrey Mashenkov

> Sql. Ensure that integration tests that use index value lookups use a plan 
> with search bounds
> ---------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-26029
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26029
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql ai3
>            Reporter: Pavel Pereslegin
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, intergration tests for checking index usage use 
> QueryChecker.matches(containsIndexScan(...
> However, containsIndexScan only checks for index usage, but does not check 
> for presence of search bounds.
> This can lead to hidden errors, in some cases we may expect to go to the 
> index with a specific key, but instead we get a full index scan.
> Therefore, the following proposal arose.
> Change the current behavior of {{containsIndexScan()}} so that it checks by 
> default that some search bounds are present.
> And add a method {{containsIndexScanWithoutSearchBounds()}} (naming is 
> discussable) that will not check for the presence of search bounds.
> Run SQL integration tests on TC and look at the failed tests.
> * If the test uses the index for ordering or this is expected behavior - 
> change it to use {{containsIndexScanWithoutSearchBounds}}
> * If the index search is performed incorrectly, create a corresponding JIRA 
> issue to fix it and mute the corresponding test.



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

Reply via email to