-
Notifications
You must be signed in to change notification settings - Fork 19
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
how to visualize SPARQL queries and execution plans #203
Comments
To visualize execution plans we first need a standard to describe a query plan. This would be good to do to share development resources. |
I think these are really useful to quickly visualize query patterns (as are algebra visualizations – they just visualize different things). Regarding query plans, I've used mermaid to play around with visualizing query plans coming out of Neptune in the past, with some success. I think the challenge is that query plans from different systems can look very different (not just different operators, but also structurally different), so may be difficult to visualize in a common way while supporting plans from disparate systems. |
|
It sounds like you want more than the algebraic structure so that it also shows variable co-occurrence? I don't have anything like that, and think that might be more confusing than useful (?). Here's part of a Neptune explain visualized using mermaid (this happens to be an OpenCypher query, but the explain format is basically the same for SPARQL). This is a very generic data flow diagram with operators as nodes, with no real specialization for specific operators: |
an authenticated user has these available from the html result page. |
(This merely promotes a good
practice
and asks for more ideas)@JervenBolleman makes some amazing SPARQL visualizations.
See eg https://sib-swiss.github.io/sparql-examples/examples/dbgi/001.html .
This is a rather complex query, and the diagram really helps to understand it and debug it (eg you'd see immediately if some var is misspelled):
The diagram is SVG and is made with:
Questions:
A related need is to visualize execution PLANS.
The text was updated successfully, but these errors were encountered: