Pascal/allow field require update - #1103
Merged
Merged
Conversation
Pascal-Delange
force-pushed
the
pascal/allow-field-require-update
branch
from
September 12, 2025 09:01
feb4c23 to
668d3d1
Compare
Pascal-Delange
enabled auto-merge (rebase)
September 12, 2025 09:01
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
2 participants
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.
Context
The new public API v1 rejects "additional properties", to reduce the risk of customers accidentally sending incorrect fields on the ingestion or decision API.
This also means it's no longer possible to add a field to the ingestion pipeline, then to the data model.
As a consequence, it was no longer possible to add a required field to a table that's used with real time API (not without downtime).
In this PR:
Prerequisite
checkmarble/marble-backend#1192
Screenshots