Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Recap schema registry #401

Merged
merged 1 commit into from
Oct 5, 2023
Merged

Add Recap schema registry #401

merged 1 commit into from
Oct 5, 2023

Commits on Oct 5, 2023

  1. Add Recap schema registry

    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 committed Oct 5, 2023
    Configuration menu
    Copy the full SHA
    53bc3f7 View commit details
    Browse the repository at this point in the history