[jira] [Commented] (IGNITE-8386) SQL: Make sure PK index do not use wrapped object

["Yury Gerzhedovich (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676419#comment-16676419 ] 

Yury Gerzhedovich commented on IGNITE-8386:
-------------------------------------------

[~vozerov],
 # Merge with recent master and resolve conflicts.
 # Add compatibility.
 # Additional tests have been added including compatibility one.

Started new TS Run all suit - [https://ci.ignite.apache.org/viewQueued.html?itemId=2254141&tab=queuedBuildOverviewTab|https://ci.ignite.apache.org/viewQueued.html?itemId=2254141&tab=queuedBuildOverviewTab88]

> SQL: Make sure PK index do not use wrapped object
> -------------------------------------------------
>
>                 Key: IGNITE-8386
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8386
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.4
>            Reporter: Vladimir Ozerov
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>              Labels: iep-19, performance
>             Fix For: 2.8
>
>
> Currently PK may be built over the whole {{_KEY}} column, i.e. the whole binary object. This could happen in two cases:
> 1) Composite PK
> 2) Plain PK but with {{WRAP_KEY}} option.
> This is critical performance issue for two reasons:
> 1) This index is effectively useless and cannot be used in any sensible queries; it just wastes space and makes updates slower
> 2) Binary object typically has common header bytes what may lead to excessive number of comparisons during index update.
> To mitigate the problem we need to ensure that index is *never* built over {{_KEY}}, Instead, we must always extract target columns and build normal index over them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)