Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the controller for topic metadata requests #1995

Merged
merged 2 commits into from
Feb 6, 2020

Conversation

TylerLubeck
Copy link
Contributor

@TylerLubeck TylerLubeck commented Feb 6, 2020

Closes #1994


This change is Reviewable

@@ -473,7 +473,7 @@ def delete_topics(self, topics, timeout_ms=None):
return response


def _get_cluster_metadata(self, topics=None, auto_topic_creation=False):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it'd be cleaner if we could specify the broker ID here, and then the caller can pass in a function that identifies the controller... but looks like that's not how self._send_request_to_controller() is wired up. And it'd be hard to change because of needing to handle retries. So let's just go with this as-is (especially since it's non-public).

@jeffwidman
Copy link
Collaborator

I'll wait for travis and then will merge.

Be nice to have tests for this describe/list topics stuff, but I'm going to merge this one regardless since it's a clear bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

describe topics needs to speak to the controller
2 participants