[IGNITE-16093] Thin 3.0: Handle absent and null values differently

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha3
• Fix Version/s: 3.0.0-alpha4
• Component/s: thin client
• Labels: ignite-3
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 09/Dec/21 11:50
• Updated: 17/Dec/21 14:25
• Resolved: 17/Dec/21 11:20

Description

Currently, thin client protocol has no distinction between "no value" and "null value" when serializing tuples. But there is a difference on the server when handling NOT NULL columns and default values.

Update the protocol and implementation to indicate when a column value was not set or set to null explicitly.

Issue Links

• links to: GitHub Pull Request #513
• links to: GitHub Pull Request #513