You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Joel Lang (JIRA)" <ji...@apache.org> on 2018/05/01 09:23:00 UTC
[jira] [Commented] (IGNITE-8384) SQL: Secondary indexes should sort
entries by links rather than keys
[ https://issues.apache.org/jira/browse/IGNITE-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459550#comment-16459550 ]
Joel Lang commented on IGNITE-8384:
-----------------------------------
How much of an impact would this have on the amount of page reads necessary to add a new entry to the index?
> SQL: Secondary indexes should sort entries by links rather than keys
> --------------------------------------------------------------------
>
> Key: IGNITE-8384
> URL: https://issues.apache.org/jira/browse/IGNITE-8384
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.4
> Reporter: Vladimir Ozerov
> Priority: Major
> Labels: iep-19, performance
> Fix For: 2.6
>
>
> Currently we sort entries in secondary indexes as {{(idx_cols, KEY)}}. The key itself is not stored in the index in general case. It means that we need to perform a lookup to data page to find correct insertion point for index entry.
> This could be fixed easily by sorting entries a bit differently - {{idx_cols, link}}. This is all we need.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)