[
https://issues.apache.org/jira/browse/IGNITE-17536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17536:
-------------------------------------
Description:
In a simple implementation, instead of a *BinaryTuple*, we store its link from
the *FreeList* in the key, this is not optimal and we need to inline the
*BinaryTuple* in the key, for starters, you can see how to do this in 2.0.
What should be done:
* Calculate approximate inline size;
* Write *BinaryTuple* as is up to inline size;
was:In a simple implementation, instead of a *BinaryTuple*, we store its link
from the *FreeList* in the key, this is not optimal and we need to inline the
*BinaryTuple* in the key, for starters, you can see how to do this in 2.0.
> Implement BinaryTuple inlining in a hash index B+Tree
> -----------------------------------------------------
>
> Key: IGNITE-17536
> URL: https://issues.apache.org/jira/browse/IGNITE-17536
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> In a simple implementation, instead of a *BinaryTuple*, we store its link
> from the *FreeList* in the key, this is not optimal and we need to inline the
> *BinaryTuple* in the key, for starters, you can see how to do this in 2.0.
> What should be done:
> * Calculate approximate inline size;
> * Write *BinaryTuple* as is up to inline size;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
