feat: add explain TableFunction for substrait #114
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.
This adds a new table function,
explain_substrait
, as well as a new execution kernel for the function and binding kernel. This reuses theFromSubstraitFunctionData
structure since it contains all the pieces we would need.The reason this is useful is because
explain
naively returns the table function itself instead of the plan it may execute. In the case of executing substrait (e.g.from_substrait(...)
), this would be a single operator for thefrom_substrait
function itself. If, instead one callsexplain_substrait(...)
, the result would be an explain plan for what the substrait extension translates into duckdb (the result of SubstraitPlanToDuckDBRel)