As-a-service, consume topic definitions and act accordingly #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
My ambition to manage schemas in topic declarations got dented by the behavior or REST Proxy, which requires producers to have either the full schema or the schema I abandoned this PR for a separate module, https://github.com/Yolean/kafka-topic-manager, that tries more optimistic use of Schema Registry + REST Proxy. Will try to track overall progress, or lack thereof, in Yolean/kubernetes-kafka#101. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An experiment with the Kafka's AdminClient API and with declarative topic and schema management. The sequel to a hack that investigated the Kubernetes "operator" + CRD pattern. Consuming CRDs we'd have to reinvent Kafka's consumer commit concept, so I thought that definitions are better kept in a topic.