This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
[BUG] Provide cache mechanism for KafkaTopicManager and KafkaTopicConsumerManager #38
Comments
Demogorgon314
pushed a commit
to Demogorgon314/kop
that referenced
this issue
Aug 14, 2023
### Motivation [KIP-135](https://cwiki.apache.org/confluence/display/KAFKA/KIP-135+%3A+Send+of+null+key+to+a+compacted+topic+should+throw+non-retriable+error+back+to+user) ### Modifications Validate null-key for compacted topic
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
KafkaTopicManager provided a way to hold on-going topics. it need a cache mechanism to evict invalid/old data.
we could use KafkaTopicManager as cache for
MetadataCache(in KafkaApis.scala), to returnTo Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: