You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/20 14:24:00 UTC
[jira] [Commented] (IGNITE-9519) Composite types should be inlined
in index tree
[ https://issues.apache.org/jira/browse/IGNITE-9519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622122#comment-16622122 ]
ASF GitHub Bot commented on IGNITE-9519:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4724
> Composite types should be inlined in index tree
> -----------------------------------------------
>
> Key: IGNITE-9519
> URL: https://issues.apache.org/jira/browse/IGNITE-9519
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.6
> Reporter: Yury Gerzhedovich
> Assignee: Stanislav Lukyanov
> Priority: Major
> Fix For: 2.7
>
>
> Currently in case PK is complex type it can not be keep at inline index.
> This is critical performance issue due to for any put or get operation it cant' be fully comparable and require read full object from the heap or even disk storage.
> To mitigate the problem we need add ability keep complex type (java object) at inline indexes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)