Repository navigation
Track explicit Snowflake SQL TRY_CAST without affecting cast fast paths - #165
Merged
osipovartem merged 2 commits intoOct 25, 2026
Merged
Conversation
osipovartem
force-pushed
the
df55-explicit-try-cast-origin
branch
from
October 25, 2026 17:24
0bc89d6 to
b81c3a3
Compare
osipovartem
merged commit Oct 25, 2026
6770c7c
into
df55-physical-udf-instance
37 of 38 checks passed
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.
Purpose
Preserve provenance of explicit Snowflake SQL
TRY_CASTso Rustice can validate source types after parameter binding without changing internal DataFusionTryCastexpressions.Behavior
TRY_CASTplanned under the Snowflake dialect; generic SQL,SAFE_CAST, and planner-inserted casts remain unmarked.EXPLAINoutput.Verification
cargo +1.99.0 fmt --all -- --checkandgit diff --checkpassed on the rebased branch.