[ https://issues.apache.org/jira/browse/IGNITE-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474255#comment-16474255 ]
Vladimir Ozerov commented on IGNITE-8384: ----------------------------------------- [~langj], this should reduce number of page reads. > 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. > UPD: If we have an affinity keys, then affinity column will be added to > secondary index as well. > So, we'll have secondary index as {{(idx_cols, KEY, AFF_COL)}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)