You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2024/08/01 19:10:00 UTC
[jira] [Updated] (KAFKA-17033) Consider replacing the type of the ReplicaKey directory id field.
[ https://issues.apache.org/jira/browse/KAFKA-17033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin McCabe updated KAFKA-17033:
---------------------------------
Parent: (was: KAFKA-14094)
Issue Type: Bug (was: Sub-task)
> Consider replacing the type of the ReplicaKey directory id field.
> -----------------------------------------------------------------
>
> Key: KAFKA-17033
> URL: https://issues.apache.org/jira/browse/KAFKA-17033
> Project: Kafka
> Issue Type: Bug
> Reporter: José Armando García Sancio
> Priority: Major
>
> The current type for directoryId field in ReplicaKey is Optional<Uuid>. The field is Optional.empty when the directory id is Uuuid.ZERO_UUID. This nice because if forces KRaft to handle the empty care differently.
> The issue with this modeling is that anytime KRaft needs to serialize the directory it does an explicit conversion to the zero uuid when the option is empty.
> It is possible that adding a type like DirectoryId could improve the user experience when dealing with the directory uuid.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)