Add Recap schema registry #401
Merged
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
Recap can now store schemas in a registry similar to [Confluent's schema registry](https://docs.confluent.io/platform/current/schema-registry/index.html) and [Buf's schema registry](https://buf.build/product/bsr). The registry is meant to be used as a source of truth for Recap schema definitions in an organization. It can also be used as a cache for schemas that have been read from elsewhere, though it is not meant to be a general purpose data catalog (i.e. data discoverability is not the goal). There are two components to the registry: - Storage - HTTP/JSON API The storage layer stores schemas on a filesystem like S3, GCS, or the local filesystem using [fsspec](https://filesystem-spec.readthedocs.io/en/latest/). The HTTP/JSON layer is a Flask app that exposes a REST API for interacting with the registry. The API largely mirrors Confluent's API, but with slightly different paths. It also doesn't have a delete endpoint.
criccomini
force-pushed
the
add-registry
branch
from
6db4b21
to
53bc3f7
Compare
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.
Recap can now store schemas in a registry similar to Confluent's schema registry and Buf's schema registry.
The registry is meant to be used as a source of truth for Recap schema definitions in an organization. It can also be used as a cache for schemas that have been read from elsewhere, though it is not meant to be a general purpose data catalog (i.e. data discoverability is not the goal).
There are two components to the registry:
The storage layer stores schemas on a filesystem like S3, GCS, or the local filesystem using fsspec. The HTTP/JSON layer is a Flask app that exposes a REST API for interacting with the registry.
The API largely mirrors Confluent's API, but with slightly different paths. It also doesn't have a delete endpoint.