[
https://issues.apache.org/jira/browse/IGNITE-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-18370:
--------------------------------------
Fix Version/s: 3.0.0-beta2
> Migrate rest of the core modules to BinaryTuple
> -----------------------------------------------
>
> Key: IGNITE-18370
> URL: https://issues.apache.org/jira/browse/IGNITE-18370
> Project: Ignite
> Issue Type: Improvement
> Reporter: Konstantin Orlov
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Binary Tuple Format was introduced in IEP-92 as replacement of IEP-54
> Binary Row. However, the Ignite's core is still operating rows in BinaryRow
> format. This is follow up ticket for IGNITE-18360, and it covers the rest of
> the core.
> Definition of done of current ticket is zero usage of BinaryRow in core
> modules ({{ignite-index}}, {{ignite-schema}}, {{ignite-sql-engine}},
> {{ignite-storage-api}}, {{ignite-storage-page-memory}},
> {{ignite-storage-rocksdb}}, {{ignite-table}}; it may be used by clients
> though).
> One of the possible approach to done this task is just to drop BinaryRow
> class and then restore compilation of the project step-by-step migrating
> components to a new format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
