[
https://issues.apache.org/jira/browse/IGNITE-9519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610542#comment-16610542
]
ASF GitHub Bot commented on IGNITE-9519:
----------------------------------------
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/4724
IGNITE-9519: PK as complex type should can be keep at inline index
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9519
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4724.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4724
----
commit 8b96932e622afdd79fb4cc62b6e5ce0ddf0f497f
Author: Yury Gerzhedovich <ygerzhedovich@...>
Date: 2018-09-10T15:42:14Z
IGNITE-9519: PK as complex type should can be keep at inline index
----
> PK as complex type should can be keep at inline index
> -----------------------------------------------------
>
> Key: IGNITE-9519
> URL: https://issues.apache.org/jira/browse/IGNITE-9519
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.6
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
>
> 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)
