[IGNITE-17297] Thin 3.0: Adopt BinaryTuple format in transport layer

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: platforms, thin client
• Labels: iep-92 ignite-3
• Epic Link: Binary Tuple
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 04/Jul/22 10:55
• Updated: 28/Feb/23 16:35
• Resolved: 09/Sep/22 11:35

Description

BinaryTuple (see IEP-92) is a common format for data exchange in Ignite 3. Adopt it in the thin client protocol to be able to avoid intermediate conversions when exchanging data.

For example, we should be able to write SQL query results to the client socket directly as byte[].

 

Update IEP-76 when done.

Issue Links

• blocks: IGNITE-17392 Thin 3.0: Partition Awareness
• blocks: IGNITE-18922 Thin 3.0: Avoid BinaryTuple conversion in client SQL handler
• blocks: IGNITE-17632 Thin 3.0: Support decimal scale in client schema
• blocks: IGNITE-17636 Thin 3.0: Avoid BinaryTuple conversion in client handler
• blocks: IGNITE-18925 Thin 3.0: Avoid BinaryTuple conversion from client to storage
• is blocked by: IGNITE-17583 Extract BinaryTuple into a separate module to reuse on client
• is blocked by: IGNITE-17593 .NET: Thin 3.0: Implement BinaryTuple serialization
• relates to: IGNITE-18395 .NET: Thin 3.0: Remove MessagePack library dependency
• links to: GitHub Pull Request #1058
• links to: IEP-76 Thin Client Protocol for Ignite 3.0 - Apache Ignite - Apache Software Foundation
• links to: IEP-92 Binary Tuple