[
https://issues.apache.org/jira/browse/IGNITE-21506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reassigned IGNITE-21506:
-----------------------------------------
Assignee: Konstantin Orlov
> Refactoring of tuple marshaller
> -------------------------------
>
> Key: IGNITE-21506
> URL: https://issues.apache.org/jira/browse/IGNITE-21506
> Project: Ignite
> Issue Type: Improvement
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> At the moment, tuple marshaller (see
> {{org.apache.ignite.internal.schema.marshaller.TupleMarshallerImpl}}) follow
> the IEP-54 strategy, implying that table row is split on two chunk, and every
> chunk is marshalled separately one after another. Although it creates
> byte-wise equal table row, the approach is questionable because now we have
> no chunks, and columns both of key and value are marshalled in a common
> space. Besides, segregation on two chunks make it harder to get rid of IEP-54
> leftovers completely, because in fact key and value columns should not
> necessary take contiguous space (meaning that layout `val1, id1, val2, id2'
> is valid)).
> Let's simplify tuple marshaller in order to reflect actual state of the
> project and prepare ground to completely get rid of IEP-54.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
