-
Notifications
You must be signed in to change notification settings - Fork 1
Add truncate statement support #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-42.0.0
Are you sure you want to change the base?
Conversation
7ea6796
to
ca47b51
Compare
ca47b51
to
177048f
Compare
177048f
to
4fb5e19
Compare
4fb5e19
to
a31a6e1
Compare
@@ -1228,6 +1228,10 @@ impl DefaultPhysicalPlanner { | |||
"Unsupported logical plan: Analyze must be root of the plan" | |||
) | |||
} | |||
LogicalPlan::Truncate(_) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it required to extend LogicalPlan
enum? Isn't LogicalPlan::Extension
not enough for our purposes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't considered this option. It might suit this case better. That way, we can move all the additional logic inside TCS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, here an example of such approach:
Own extensions for prepare
, execute
, and deallocate
(prepared statements stuff).
And physical planning for extensions in the custom planner:
This PR adds TRUNCATE operation to LogicalPLan enum.