[
https://issues.apache.org/jira/browse/IGNITE-24664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932172#comment-17932172
]
Ignite TC Bot commented on IGNITE-24664:
----------------------------------------
{panel:title=Branch: [pull/11900/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11900/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8330663&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Use _key_PK index scan instead of hash index scan if possible
> -----------------------------------------------------------------------------
>
> Key: IGNITE-24664
> URL: https://issues.apache.org/jira/browse/IGNITE-24664
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Looks like _key_PK index scan is more effective than hash index scan. Hash
> index scan requires also entity type check, but _key_PK index scan only built
> for required entity type, so type check can be skipped.
> H2 engine uses PK index scan for table scans (see H2TableScanIndex.delegate()
> method).
> Calcite engine should also use PK index scan when indexes are in correct
> state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
