Description
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.
Attachments
Issue Links
- blocks
-
IGNITE-18922 Thin 3.0: Avoid BinaryTuple conversion in client SQL handler
- Open
- is related to
-
IGNITE-18360 Migrate storage to new Binary Tuple format
- Resolved
- split from
-
IGNITE-18288 Investigation of migration BinaryRow -> BinaryTuple
- Resolved
- links to