We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, it's difficult to tell which state table belongs to which part of the execution plan.
We may provide a syntax like
explain <table_or_mv_or_sink_name>
and then it will print a physical plan (i.e. fragments) with the real IDs, including (and not limited to) fragment_id, table id and names, etc.
This is an alternative to the dashboard. Would be helpful when we can't access the dashboard easily.
No response
The text was updated successfully, but these errors were encountered:
thinking it can be integrated into the diagnose command, users just one click and print all the query plans for off-site debugging
diagnose
Sorry, something went wrong.
Right. That's also what I think.
shanicky
No branches or pull requests
Is your feature request related to a problem? Please describe.
Currently, it's difficult to tell which state table belongs to which part of the execution plan.
Describe the solution you'd like
We may provide a syntax like
and then it will print a physical plan (i.e. fragments) with the real IDs, including (and not limited to) fragment_id, table id and names, etc.
Describe alternatives you've considered
This is an alternative to the dashboard. Would be helpful when we can't access the dashboard easily.
Additional context
No response
The text was updated successfully, but these errors were encountered: