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.

Sign up for GitHub

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

Jump to bottom

Pre-emptively look up Topic-id -> Name mappings on startup. #6

Open
robobario opened this issue Jun 21, 2023 · 2 comments
Open

Pre-emptively look up Topic-id -> Name mappings on startup. #6

robobario opened this issue Jun 21, 2023 · 2 comments

Comments

@robobario
Copy link

Once we have #3 implemented then we will have a set of policies configured that will be targeting specific topic names, or using a wildcard to target any topic.

If there are any wildcard policies: we could make a metadata request to describe all the topics in existence and cache their UUIDs to name.

If there are only policies for specific topics: we can request the UUIDs just for those topics.
@robobario
Copy link
Author

startup might be not quite the right term, we could probably trigger it during the first intercepted FetchRequest

@robobario
Copy link
Author

Added a discussion to see if we can support per-virtual-cluster state better in Kroxylicious

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@robobario