Repository navigation
feat: define immutable WAL ingestion contracts - #384
Merged
Merged
Conversation
50 of 62 tasks
This file contains hidden or 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
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.
Summary
Ingress and materializers need the same immutable routing keys, schema identity, write policy and record limits before accepting a table generation. Add an independent
contractfeature with serializable metadata, explicit validation errors and a domain-separated schema fingerprint. It requires neither Arrow nor a replication engine. Callers still enforce durable binding, validate actual payloads and provide authentication and ID uniqueness.Fixed synthetic binary/hash fixtures preserve the metadata representation. CI exercises the optional feature. Production ingestion is unchanged.
Refs #378.
Testing