[
https://issues.apache.org/jira/browse/IGNITE-28331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-28331:
-------------------------------------
Description:
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.
was:
I discovered that for a simple pk (consisting of one column), queries like
"select name from person where id = ?" 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.
> 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: Improvement
> Affects Versions: 2.17
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-2
> Time Spent: 40m
> 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)
