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
{{ message }}
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Kafka 2.8 introduced Topic ID's (KIP 516). Since Kafka 3.1.0, FETCH requests use topic IDs instead of topic names.
The current implementation of topic encryption uses string-matching to identify topic partitions in Kafka messages. This needs to be extended to recognize topics based on topic ID.
This presumably means:
Message handling must recognize both topic names and topic id's.
The topic encryption service must maintain topic metadata for all topics in order to efficiently map topic id's to names.
Encryption policy could be specified with topic names or IDs.
The text was updated successfully, but these errors were encountered:
Kafka 2.8 introduced Topic ID's (KIP 516). Since Kafka 3.1.0, FETCH requests use topic IDs instead of topic names.
The current implementation of topic encryption uses string-matching to identify topic partitions in Kafka messages. This needs to be extended to recognize topics based on topic ID.
This presumably means:
The text was updated successfully, but these errors were encountered: