[DJ Semantic Fingerprint 3] Add semantic fingerprints to deployment impact - #2483
Open
philipfweiss wants to merge 8 commits into
Open
[DJ Semantic Fingerprint 3] Add semantic fingerprints to deployment impact#2483philipfweiss wants to merge 8 commits into
philipfweiss wants to merge 8 commits into
Conversation
philipfweiss
marked this pull request as ready for review
September 1, 2026 18:51
philipfweiss
marked this pull request as draft
September 1, 2026 22:10
philipfweiss
changed the base branch from
semantic-node-fingerprints
to
semantic-fingerprint-deployment-graph
September 1, 2026 23:14
philipfweiss
marked this pull request as ready for review
September 1, 2026 23:27
philipfweiss
force-pushed
the
semantic-fingerprint-deployment-graph
branch
from
September 2, 2026 01:53
da0a6ef to
1783278
Compare
philipfweiss
force-pushed
the
semantic-fingerprints-deployment-impact-api
branch
from
September 2, 2026 01:53
1c628be to
d914195
Compare
philipfweiss
force-pushed
the
semantic-fingerprint-deployment-graph
branch
from
September 2, 2026 19:46
1783278 to
de5ed41
Compare
philipfweiss
force-pushed
the
semantic-fingerprints-deployment-impact-api
branch
2 times, most recently
from
September 3, 2026 01:29
63bf44c to
638e8b5
Compare
philipfweiss
force-pushed
the
semantic-fingerprint-deployment-graph
branch
from
September 3, 2026 19:27
1ebbd8d to
a7a25ff
Compare
philipfweiss
force-pushed
the
semantic-fingerprints-deployment-impact-api
branch
2 times, most recently
from
September 3, 2026 21:34
84419d8 to
1d4520e
Compare
Base automatically changed from
semantic-fingerprint-deployment-graph
to
main
September 4, 2026 20:15
added 4 commits
September 4, 2026 13:17
Return server-owned fingerprints and change tiers for deployment results and downstream impacts, including client parsing and unknown-state propagation.
Impact tests now derive expected hashes from complete graph snapshots, matching production parent resolution.
Recover per node during impact analysis so invalid SQL can produce unknown fingerprints without weakening normal deployment parsing.
philipfweiss
force-pushed
the
semantic-fingerprints-deployment-impact-api
branch
from
September 4, 2026 20:21
1d4520e to
52d4f75
Compare
✅ Deploy Preview for thriving-cassata-78ae72 canceled.
|
added 4 commits
September 4, 2026 14:19
Canonicalize required-dimension identities during change detection so equivalent metric specs remain no-ops, and align deployment assertions with the additive fingerprint response fields.
Preserve namespace rendering during semantic comparison so unchanged deployments remain no-ops.
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.
/deployments/impactreports operations and changed fields without a server-owned semantic identity. Metadata consumers otherwise have to repeat DJ's classification, SQL handling, and graph traversal.Depends on #2488.
This PR:
change_tierandsemantic_fingerprintfieldsdeploy_typeand parses old and new response shapes in the Python clientImpact propagation example
flowchart LR X{"orders table changes"} S["source: orders<br/>object hash: h_orders to h_orders_next<br/>operation: update<br/>direct tier: major"] T["transform: clean_orders<br/>object hash: h_clean_orders to h_clean_orders_next<br/>operation: noop<br/>direct tier: none"] M["metric: order_count<br/>object hash: h_order_count to h_order_count_next<br/>operation: noop<br/>direct tier: none"] C["cube: orders_cube<br/>object hash: h_orders_cube to h_orders_cube_next<br/>operation: noop<br/>direct tier: none"] X --> S S ==>|h_orders changed| T T ==>|h_clean_orders changed| M M ==>|h_order_count changed| C classDef direct fill:#fff1d6,stroke:#c2410c,color:#431407 classDef propagated fill:#dbeafe,stroke:#2563eb,color:#172554 class S direct class T,M,C propagatedThe metadata rows become
source::orders::h_orders_next,transform::clean_orders::h_clean_orders_next,metric::order_count::h_order_count_next, andcube::orders_cube::h_orders_cube_next. All four CODEOWNERS are therefore included in review.Verification:
Started this branch on development slot 1:
Then deployed a source, transform, and metric before changing only the source table and calling
POST /deployments/impact:Observed:
{ "status": 200, "results": [ { "name": "fingerprint_verification.transform", "operation": "noop", "change_tier": "none", "semantic_fingerprint": { "version": 1, "digest": "396e92df092afb466e34ef038b4bd6b2987b6ec09b1f39700f5d1cbf649e3c71" }, "hash_changed": true }, { "name": "fingerprint_verification.metric", "operation": "noop", "change_tier": "none", "semantic_fingerprint": { "version": 1, "digest": "3f6230e34838ea84ca8cd10ce6b4049b45b3ff79cf2e9840a419ade1731d19d2" }, "hash_changed": true }, { "name": "fingerprint_verification.source", "operation": "update", "change_tier": "major", "semantic_fingerprint": { "version": 1, "digest": "dd0e10eeead298cdb31af85f3ccd3dac98760564c4d1f97473eb25bc5d024e98" }, "hash_changed": true } ] }Semantic fingerprint stack
This is PR 3 of 4: