Revise node attributes after sealing while keeping provenance - #7548
Draft
agoscinski wants to merge 3 commits into
Draft
Revise node attributes after sealing while keeping provenance#7548agoscinski wants to merge 3 commits into
agoscinski wants to merge 3 commits into
Conversation
Introduce NEXT_VERSION links and lineage metadata for immutable copy-on-write revisions of Data nodes. Expose version navigation, explicit lineage loading, and query support for version, lineage_uuid, and is_head. Add migrations and regression coverage for storage, graph traversal, archive import, and CLI traversal rules.
Cover the confirmed Data-only revision scope by checking that process nodes cannot be revised. Add SQLite DOS migration coverage for the versioned-node schema changes, including unique constraint enforcement and downgrade cleanup.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: QUIET Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Allows to change the nodes attributes after sealing while the provenance is tracked. A new node is created with a link from the old one. One can reference the nodes individually by a uuid or by the lineage uuid and a version number. My main motivation is to stop this
setupvsconfiguresplit in the computer which seamed always arbitrary.Example