0.101.0 (2026-08-16)
⚠ BREAKING CHANGES
- extensions:
extensions/extension_types.yamland
extensions/type_variations.yamlare no longer part of the extension
catalog. They move tosite/examples/extensions/, and their URNs change
fromextension:io.substrait:extension_typesand
extension:io.substrait:type_variationsto
extension:org.example:extension_typesand
extension:org.example:type_variations.
Consumers that resolve extension:io.substrait:extension_types — the
point/line user-defined types, which substrait-java and substrait-go
both register today — will no longer find it in the catalog, and should
either define those types locally or load the example explicitly under
its new URN.
The remaining example files keep their location but also move to the
extension:org.example: owner, including
lambda_function_example.yaml, which previously duplicated the official
extension:io.substrait:functions_list URN.
Nothing in the extension:org.example: namespace carries a
compatibility guarantee: those files exist to illustrate the extension
schema and to serve as parser fixtures, and may change without a
deprecation cycle.
- protos:
Expression.FieldReference.OuterReference.steps_out
is deprecated in favor ofrel_reference, which names the binding
relation via its plan-wide uniqueRelCommon.rel_anchorand therefore
resolves unambiguously in DAG-shaped plans with shared relations
(ReferenceRel), where counting subquery boundaries upward does not.
Consumers should addrel_referencesupport before producers switch to
it. Note that both fields are members of the sameouter_reference_type
oneof, so a plan cannot carry both forms at once: the migration is
consumer-first rather than dual-write. Nothing is removed by this
change: the deprecation is metadata only, consumers are not required to
understand or validate it, and no existing plan changes meaning.
steps_outremains fully functional and is scheduled for removal in a
later release.