You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2021/12/16 14:27:00 UTC
[jira] (IGNITE-16093) Thin 3.0: Handle absent and null values differently
[ https://issues.apache.org/jira/browse/IGNITE-16093 ]
Pavel Tupitsyn deleted comment on IGNITE-16093:
-----------------------------------------
was (Author: ptupitsyn):
Looks like there is still no consensus on the desired behavior with null vs none values, so a dev list discussion is required before we start working on this.
> 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
>
>
> 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)