-
Notifications
You must be signed in to change notification settings - Fork 590
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
feat: explain a query and output a Graphviz representation of the query plan #18803
Comments
Related: #14168 |
And also #17218 |
Opening a tracking issue for these improvements to |
Currently we support structured output, so the major work is complete. We can support This can be done in the following way:
|
Hi @kwannoel , I wound like to attempt on this issue - are we aiming to support logical plan and physical plan as dot format?
looking at the code do we need to implement Deserialize for PrettySerde struct? |
Yes, via
Yes, either implement Deserialize, or if you need more control over the way |
send a draft - one more q which syntax is better |
Missed this, replied here: #19446 (comment). Thanks for your contribution! |
In the case of a large complex query, a visualized representation can be clearer to diagnose problems, e.g. easier to know which two upstream are joined together if they are separated far away in the output of
explain <SQL>
.https://github.com/risingwavelabs/risingwave/blob/main/src/frontend/src/scheduler/distributed/query.rs#L293-L294 output a task-level graphviz representation for debugging usage.
We can enable a query plan representation via the command
explain (graphviz) <SQL>
.The text was updated successfully, but these errors were encountered: