[IGNITE-16152] Thin 3.0: Optimize server-side Tuple handling using known schema version

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0.0-alpha3
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: ignite-3
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 17/Dec/21 18:22
• Updated: 04/Sep/24 16:19
• Resolved: 22/May/23 08:24

Description

Thin client protocol is schema-aware, but the known schema is thrown away on the server after deserialization, and Table API has to match it against schemas again.

SchemaAware interface can be used to preserve known schema when passing tuples to the Table API (see how TupleMarshallerImpl checks for SchemaAware).

Example: table.Upsert(Tuple t)

1. Client: match user tuple to schema, serialize with schema version, send to server
2. Server: read schema version, read tuple data, create Tuple, throw away schema version, pass to Table API
3. Server: match tuple to schema

Issue Links

• is superceded by: IGNITE-18925 Thin 3.0: Avoid BinaryTuple conversion from client to storage