Add ExtractPlan to Connection/ClientContext and add example of alternative execution engine #1897
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 PR adds an example of using an alternative execution engine with DuckDB. The essence of it is that we create some tables inside DuckDB, and then use the new ExtractPlan function to receive a fully bound and (potentially) optimized logical plan from any query we want to fire. We then have a transformer phase that transforms DuckDB's logical plan to our own (custom) physical plan and execute that plan.
Simplified/shortened code snippet: