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

Posted to jira@kafka.apache.org by GitBox <gi...@apache.org> on 2021/12/10 19:39:03 UTC

[GitHub] [kafka] ableegoldman commented on pull request #11591: KAFKA-12648: fix IllegalStateException in ClientState after removing topologies

ableegoldman commented on pull request #11591:
URL: https://github.com/apache/kafka/pull/11591#issuecomment-991243851


   The check before was essentially about two things, (a) sanity check that the ClientState methods are executed in the correct order since the task initialization ended up becoming spread out over the assignment method, and (b) verifying that the application did not try to do the exact thing that the NamedTopology feature is intended to enable, ie that the user did't try to modify the topology in an incompatible way. The check in (a) is still preserved, while the check in (b) isn't valid for NamedTopologies


-- 
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: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org