[jira] [Updated] (CASSGO-134) gocql: inconsistent unmarshaling for empty/NULL UUID to *[16]byte

["João Reis (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSGO-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

João Reis updated CASSGO-134:
-----------------------------
    Change Category: Semantic
         Complexity: Normal
      Fix Version/s: 2.2.0
          Reviewers: Bohdan Siryk, João Reis
             Status: Open  (was: Triage Needed)

> gocql: inconsistent unmarshaling for empty/NULL UUID to *[16]byte
> -----------------------------------------------------------------
>
>                 Key: CASSGO-134
>                 URL: https://issues.apache.org/jira/browse/CASSGO-134
>             Project: Apache Cassandra Go driver
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Xiaonan Chen
>            Priority: Normal
>             Fix For: 2.2.0
>
>
> *Problem*
> Currently, when unmarshaling a UUID column from Cassandra, there is an inconsistency between non-empty and empty/NULL values:
>  * Non-empty UUIDs can be successfully unmarshaled to {{*[16]byte}}
>  * Empty or NULL UUIDs fail to unmarshal to {{*[16]byte}}
> This inconsistency causes unexpected errors when handling NULL UUID values in the application, as the driver should handle both cases uniformly.
> *Proposed Fix*
> The PR modifies the unmarshaling logic to handle empty/NULL UUIDs consistently, allowing them to be unmarshaled to {{*[16]byte}} just like non-empty UUIDs.
> *Related PR*
> [https://github.com/apache/cassandra-gocql-driver/pull/1967]
> *Testing*
> The change has been tested with both non-empty and empty/NULL UUID cases to ensure consistent behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org