[jira] [Updated] (IGNITE-28331) Fix SQL select by _key for a composite pk in Calcite engine

["Kirill Tkalenko (Jira)" <ji...@apache.org>]

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

Kirill Tkalenko updated IGNITE-28331:
-------------------------------------
    Fix Version/s: 2.19

> Fix SQL select by _key for a composite pk in Calcite engine
> -----------------------------------------------------------
>
>                 Key: IGNITE-28331
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28331
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.17
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-2
>             Fix For: 2.19
>
>          Time Spent: 8h
>  Remaining Estimate: 0h
>
> I discovered that for a simple pk (consisting of one column), queries like "select name from person where _key = ?" use the pk index with a single-value lookup.
> However, if the pk is composite, a full scan of the primary key index will be used. This is neither obvious nor efficient; this needs to be fixed for the Calcite engine.



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