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/11/07 08:57:00 UTC

[jira] [Updated] (KAFKA-19870) Support nullable/non-nullable context for shared schemas

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

Lan Ding updated KAFKA-19870:
-----------------------------
    Description: 
As discussed in [https://github.com/apache/kafka/pull/20614#discussion_r2482897053],

a shared schema currently cannot differentiate between nullable and non-nullable use

cases when reused by different fields.

 

This task is to implement a solution (e.g., via a wrapper or schema enhancement) to support

this distinction, ensuring generated code and APIs correctly reflect the nullability requirement of each field.

  was:
As discussed in https://github.com/apache/kafka/pull/20614#discussion_r2482897053, a shared schema currently cannot differentiate between nullable and non-nullable use cases when reused by different fields.

This task is to implement a solution (e.g., via a wrapper or schema enhancement) to support this distinction, ensuring generated code and APIs correctly reflect the nullability requirement of each field.


> Support nullable/non-nullable context for shared schemas
> --------------------------------------------------------
>
>                 Key: KAFKA-19870
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19870
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Lan Ding
>            Assignee: Lan Ding
>            Priority: Minor
>
> As discussed in [https://github.com/apache/kafka/pull/20614#discussion_r2482897053],
> a shared schema currently cannot differentiate between nullable and non-nullable use
> cases when reused by different fields.
>  
> This task is to implement a solution (e.g., via a wrapper or schema enhancement) to support
> this distinction, ensuring generated code and APIs correctly reflect the nullability requirement of each field.



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