You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Sarama
Kafka
Go
v1.26.4
2.4.0
1.12
Configuration
N/A
Logs
N/A
Problem Description
When requesting metadata on a single topic, the sarama library will request the broker to create the topic if it does not exist. This in not always desirable, since the topic might get made with some weird broker defined configuration. Would rather that the topic were not created, and that it was just absent from the locally cached cluster metadata.
Otherwise, this forces people to use the non topic specific metadata request, which refreshes the entire cluster's metadata. If there are thousands of topics, this can be quite a performance hit.
There should be a way to request metadata on a single topic while still suppressing auto topic creation.
The text was updated successfully, but these errors were encountered:
llamahunter
changed the title
When querying metadata for a single topic, don't autocreate if nonexistant.
When querying metadata for a single topic, don't always autocreate if nonexistant.
Feb 24, 2021
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.
Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Configuration
N/A
Logs
N/A
Problem Description
When requesting metadata on a single topic, the sarama library will request the broker to create the topic if it does not exist. This in not always desirable, since the topic might get made with some weird broker defined configuration. Would rather that the topic were not created, and that it was just absent from the locally cached cluster metadata.
Otherwise, this forces people to use the non topic specific metadata request, which refreshes the entire cluster's metadata. If there are thousands of topics, this can be quite a performance hit.
There should be a way to request metadata on a single topic while still suppressing auto topic creation.
The text was updated successfully, but these errors were encountered: