lucasbru opened a new pull request, #20574:
URL: https://github.com/apache/kafka/pull/20574

   When toology not configured.
   
   In the streams group heartbeat, we validate the topology set for the group 
against the topic metadata, to generate the "configured topology" which has a 
specific number of partitions for each topic.
   
   In streams group describe, we use the configured topology to expose this 
information to the user. However, we leave the topology information as null in 
the streams group describe response, if the topology is not configured. This 
triggers an IllegalStateException in the admin client implementation.
   
   Instead, we should expose the unconfigured topology when the configured 
topology is not available, which will still expose useful information.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to