[
https://issues.apache.org/jira/browse/IGNITE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693109#comment-16693109
]
Ignite TC Bot commented on IGNITE-10217:
----------------------------------------
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2331409&buildTypeId=IgniteTests24Java8_RunAll]
> Unwrap _KEY for secondary and affinity_key indexes
> --------------------------------------------------
>
> Key: IGNITE-10217
> URL: https://issues.apache.org/jira/browse/IGNITE-10217
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
> Labels: iep-19, performance
> Fix For: 2.8
>
>
> Currently for all secondary and affinity indexes _KEY (PK) use for comparison
> order due to secondary index can be not unique. We already implemented unwrap
> _KEY for automatically created PK
> (https://issues.apache.org/jira/browse/IGNITE-8386). Need to do the same for
> _KEY in secondary and affinity indexes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
