[
https://issues.apache.org/jira/browse/KAFKA-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849028#comment-17849028
]
José Armando García Sancio commented on KAFKA-16520:
----------------------------------------------------
Yes [~nizhikov] you can take it. You'll need it for kafka-metadata-quorum
describe changes for KIP-853.
Looking at the schema changes I suggested, it looks like I never added:
{code:java}
{ "name": "CommittedVoters", "type": "[]ReplicaState", "versions": "2+" },
{code}
As suggested by the CLI output:
{code:java}
CommittedVoters: [{"id": 0, "directoryId": "UUID1", "endpoints":
[{"name": "C", "securityProtocol": "SSL", "host": "controller-0", "port":
1234}]}, {"id": 1, "directoryId": "UUID2",
"endpoints": [{"name": "C", "securityProtocol": "SSL", "host": "controller-1",
"port": 1234}]}] {code}
I updated the KIP to include this new field in the response.
As I mentioned in the other Jira you won't be able to implement it fully since
I haven't implemented that functionality in the core KRaft implement but we can
come back to it later.
> Changes to DescribeQuorum response
> ----------------------------------
>
> Key: KAFKA-16520
> URL: https://issues.apache.org/jira/browse/KAFKA-16520
> Project: Kafka
> Issue Type: Sub-task
> Components: kraft
> Reporter: José Armando García Sancio
> Assignee: José Armando García Sancio
> Priority: Major
> Fix For: 3.8.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
