[ https://issues.apache.org/jira/browse/IGNITE-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461375#comment-17461375 ]
Pavel Tupitsyn commented on IGNITE-16093: ----------------------------------------- Merged to main: a12385a9c89186cc362fba6f3e29be45de477077 > Thin 3.0: Handle absent and null values differently > --------------------------------------------------- > > Key: IGNITE-16093 > URL: https://issues.apache.org/jira/browse/IGNITE-16093 > Project: Ignite > Issue Type: Improvement > Components: thin client > Affects Versions: 3.0.0-alpha3 > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > 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. -- This message was sent by Atlassian Jira (v8.20.1#820001)