Repository navigation
feat(core)!: bump substrait to v0.104.0 - #1404
Conversation
Spec v0.104.0 fixes two parse rules in the type-expression grammar: `!` now binds tighter than every binary operator instead of looser than `AND` / `OR`, and the `? :` conditional associates to the right. The generated parser's visitor contexts are unchanged, so `ParseToPojo` needs no change; the new behavior arrives with the `antlr` artifact. `ReturnProgramTypeTest` pinned the old `!` binding and now asserts the new one. `TestTypeParser` gains precedence cases for `!` and both conditional forms, mirroring the spec's precedence table. Closes substrait-io#1323 BREAKING CHANGE: return type expressions in extension YAMLs are parsed with `!` binding tighter than `AND` and `OR`, and with `? :` grouping to the right, which changes the result of user-defined expressions that relied on the previous binding.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
Bumps the
substrait-packagingartifacts to v0.104.0, which fixes two parse rules in the type-expression grammar (substrait-io/substrait#1228):!now binds tighter than every binary operator instead of looser thanAND/OR, and the? :conditional associates to the right. The labeled alternatives of the generated parser are unchanged, soParseToPojoneeds no change; the new behavior arrives with theantlrartifact.ReturnProgramTypeTestpinned the old!binding (!(L < 5) AND L < 0read as!((L < 5) AND (L < 0))) and now asserts the new one.TestTypeParsergains precedence cases for!and both conditional forms, taken from the spec's new precedence table.The other v0.104.0 changes (window function test-case format, test-case cleanups, site fixes) touch nothing this repo consumes.
Closes #1323
BREAKING CHANGE: return type expressions in extension YAMLs are parsed with
!binding tighter thanANDandOR, and with? :grouping to the right, which changes the result of user-defined expressions that relied on the previous binding.