Skip to content

chore: synchronize schema-options parser pin - #187

Merged
osipovartem merged 1 commit into
df55-physical-udf-instancefrom
fix/sqlparser-schema-options-pin-20261113
Nov 13, 2026
Merged

osipovartem merged 1 commit into
df55-physical-udf-instancefrom
fix/sqlparser-schema-options-pin-20261113

Conversation

@osipovartem

@osipovartem osipovartem commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator

Which issue does this PR close?

No separate issue. Coordinated parser pin for Rustice's managed CREATE SCHEMA metadata workflow.

Rationale for this change

DataFusion and downstream Rustice must share one sqlparser AST identity when retaining Snowflake schema properties.

What changes are included in this PR?

Update only the parser revision in Cargo.toml and the two matching lockfile entries to f3685b358411ba43f0f9b6fa7f50ed9de1b2b541. No DataFusion operator or planner code changes.

Are these changes tested?

The parser passes 1,599 tests and strict all-target/all-feature Clippy. Coordinated downstream builds, 4,354 owning tests, 36 SQLLogicTest unit tests, the unchanged 4,629-case Bronze baseline, and ordinary-daemon stock-connector acceptance pass. Independent source/pin review approved the exact revision.

This is downstream integration evidence, not a claim that the complete standalone DataFusion workspace Clippy/test matrix was rerun. Downstream configured all-targets Clippy and formatting also passed.

Are there any user-facing changes?

The parser retains COMMENT/retention assignments for an execution consumer. This pin does not add standalone DataFusion catalog-property execution.

@osipovartem
osipovartem merged commit dbbcfe5 into df55-physical-udf-instance Nov 13, 2026
34 of 35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant