[IGNITE-18925] Thin 3.0: Avoid BinaryTuple conversion from client to storage

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: iep-92 ignite-3
• Epic Link: Binary Tuple
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 28/Feb/23 16:35
• Updated: 04/Sep/24 16:09
• Resolved: 03/May/23 11:28

Description

IGNITE-17636 removes BinaryTuple conversion when sending data from storage to client.

This ticket is about sending data from client to storage: we read it as BinaryTuple, then convert to Tuple, then RowAssembler converts it back to BinaryTuple. Get rid of this unnecessary conversion.

Issue Links

• blocks: IGNITE-17821 Thin 3.0 Perf: Implement BinaryTupleReader and Builder over ByteBuf
• causes: IGNITE-20155 Java client connector skips NOT NULL and other column checks
• is a clone of: IGNITE-17636 Thin 3.0: Avoid BinaryTuple conversion in client handler
• is blocked by: IGNITE-17297 Thin 3.0: Adopt BinaryTuple format in transport layer
• supercedes: IGNITE-16152 Thin 3.0: Optimize server-side Tuple handling using known schema version
• links to: GitHub Pull Request #2004
• links to: IEP-92
• links to: IGNITE-18925 Avoid BinaryTuple conversion from client to storage by ptupitsyn · Pull Request #2004 · apache/ignite-3