[jira] [Updated] (IGNITE-15522) IndexQuery should perform index scan if no criteria set

["Maksim Timonin (Jira)" <ji...@apache.org>]

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

Maksim Timonin updated IGNITE-15522:
------------------------------------
    Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)
    Release Note: IndexQuery can scan PK indexes

> IndexQuery should perform index scan if no criteria set
> -------------------------------------------------------
>
>                 Key: IGNITE-15522
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15522
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: IEP-71
>             Fix For: 2.12
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently impossible to return full index range with existing IndexQuery criteria. There are  workarounds like `lte(Integer.MAX_VALUE)`. But it will be much better enable index scan by default if not criteria set. It's useful by reasons:
>  # In some cases IndexQuery is faster then ScanQuery. Then IndexQuery should have same API as ScanQuery for such cases - new IndexQuery(tbl, idxName)
>  # IndexQuery criteria performs AND operation. There is no way to set OR. setFilter is only way to specify custom rule non-AND rule for IndexQuery. So we need allow to use only filter without any criteria.
>  
> If index name isn't specified then IndexQuery should take PK index of specified table.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)