Repository navigation
fix(embedding): preserve retained casts and protect destructive MO inputs - #30
Merged
aunjgr merged 6 commits intoOct 11, 2026
Conversation
aunjgr
marked this pull request as ready for review
October 10, 2026 20:06
This was referenced Oct 11, 2026
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.
Public MatrixOne TPC-H execution exposed two GPU correctness failures: Q7 failed on a retained VARCHAR identity cast, and Q15 could silently split a destructive MO input between consumers of a shared CTE.
Exact Substrait preparation skips DuckDB's ordinary optimizer and retains semantic
VARCHAR → VARCHARcasts. Preserve string values and validity by transferring an owned column or copying a borrowed view on the caller's stream and memory resource, instead of passing STRING to cuDF's fixed-width cast.Validate reachable read consumption through
ReferenceRelbefore admitting work. Shared references cannot replay a destructive MO input, and unreachable MO bindings cannot start producers that never receive a consumer. A single reference and immutable TAE replay remain valid. Reference expansion has explicit node/depth bounds. MatrixOne's accompanying fix gives each inlined MO occurrence an independent reader on the same snapshot; canonical SQL stays unchanged.Update the value-variant test to guard the already merged, appended exact coefficient at index 21. Its stale 21-alternative assertion prevented the owning test target from compiling. No native API or numeric ABI layout change.
Validation:
Prerequisite for MatrixOne #28968. Base:
upstream-dev-merge.