You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Lan Ding (Jira)" <ji...@apache.org> on 2025/10/25 03:22:00 UTC

[jira] [Created] (KAFKA-19833) Refactor Nullable Types to Use a Unified Pattern

Lan Ding created KAFKA-19833:
--------------------------------

             Summary: Refactor Nullable Types to Use a Unified Pattern
                 Key: KAFKA-19833
                 URL: https://issues.apache.org/jira/browse/KAFKA-19833
             Project: Kafka
          Issue Type: Improvement
          Components: clients
            Reporter: Lan Ding
            Assignee: Lan Ding


see [https://github.com/apache/kafka/pull/20614#pullrequestreview-3379156676]

Regarding the implementation of the nullable vs non-nullable types. We use 3 different approaches.
 # For bytes, we implement two independent classes BYTES and NULLABLE_BYTES.
 # For array, we use one class ArraryOf, which takes a nullable param.
 # For schema, we implement NULLABLE_SCHEMA as a subclass of SCHEMA.

We need  to pick one approach to implement all nullable types in a consistent way.



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