ExtensionRegistry currently mixes two concepts:
- extension/function catalog state
- numeric anchor assignment
But extension_urn_anchor and function_anchor values are plan-local in Substrait. Reusing them as registry-level state makes ExtensionRegistry awkward to use as a pure catalog or with plans produced elsewhere.
It would be useful to separate the plan-independent extension catalog from per-plan anchor allocation/tracking.
ExtensionRegistrycurrently mixes two concepts:But
extension_urn_anchorandfunction_anchorvalues are plan-local in Substrait. Reusing them as registry-level state makesExtensionRegistryawkward to use as a pure catalog or with plans produced elsewhere.It would be useful to separate the plan-independent extension catalog from per-plan anchor allocation/tracking.