[IGNITE-17583] Extract BinaryTuple into a separate module to reuse on client

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha5
• Fix Version/s: 3.0.0-beta1
• Component/s: thin client
• Labels: iep-92 ignite-3
• Epic Link: Binary Tuple
• Ignite Flags: Docs Required, Release Notes Required

Language

Java

• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 26/Aug/22 15:12
• Updated: 13/Oct/22 12:00
• Resolved: 29/Aug/22 12:30

Description

BinaryTuple related types are currently located in ignite-schema module and coupled to internal schema-related types like NativeTypeSpec.
However, those schema-related things are not required for building and parsing binary tuples.

• Decouple the logic from internal schema types.
• Move to a separate module that can be referenced from client module.

Issue Links

• blocks: IGNITE-17297 Thin 3.0: Adopt BinaryTuple format in transport layer
• links to: GitHub Pull Request #1040
• links to: IGNITE-17583 Extract BinaryTuple core parts into a separate module by ptupitsyn · Pull Request #1040 · apache/ignite-3