Schema Subject Promotion Evaluation

[Matthew Seal (MSeal)]

Goals

1. Basic SR CRUD
2. Start a new schema based on an existing one
3. Does a dry run of produce/consume against existing topic messages with a new / proposed schemaversion successfully parse each message
4. If there are failed parses of messages they should be clearly be bubbled up
5. Verify compatibility of new schema versions
6. Smart parsing of schema file extension for richer evaluation of elements of a schema?
7. Should not break the possible Schema Linking or rules portions of our overall "data contracts" product (based on schemas).

Non-Goals

1. Use an existing language assistant for the schema language format (e.g. not recreating Avro parsing)
2. Assist with migration of applications for use of new schema
3. Re-implementing schema compatibility logic

Background

TODO More... we want developer to comfortably use schemas in their work.

Proposal

• Verify compatibility of new schema versions
  Either help pushing a subject locally to confirm compatibility or do some static analysis to get the same outcome. For static analysis we could import schema registry and expose the logic for compatibility. To determine, what extent should we manipulate a local SR on behalf of the user.

• Spike: Research "data contracts" beyond just schemas (schema linking, rules)