You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2022/12/12 11:15:00 UTC

[jira] [Created] (IGNITE-18370) Migrate rest of the core modules to BinaryTuple

Konstantin Orlov created IGNITE-18370:
-----------------------------------------

             Summary: 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


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)