[
https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879045#action_12879045
]
Rick Hillegas commented on DERBY-4587:
--------------------------------------
Thanks, Nirmal. These look good. In particular, I like seeing the ability to
collapse and expand nodes. I was a little puzzled by the lack of a top level
level, root node. Ultimately, I would expect that at run-time, the tuples would
flow out of a single root node at the top.
This visualization is an improvement over what you can do with xml documents in
Firefox today:
1) The visualization looks cleaner--it doesn't have the distracting xml tags
mixed in with it
2) Probably this approach will work in a broader range of browsers besides
Firefox.
I was wondering about how hard a different visualization would be: Instead of a
structure which looks like a folder tree, how about something which looks more
like a left-deep tree? That's what Derby query plans are today. Extra credit if
you could expand and collapse a single node without forcing everthing to the
left to expand and collapse at the same time.
Thanks!
-Rick
> Add tools for improved analysis and understanding of query plans and
> execution statistics
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-4587
> URL: https://issues.apache.org/jira/browse/DERBY-4587
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Tools
> Reporter: Bryan Pendleton
> Assignee: C.S. Nirmal J. Fernando
> Attachments: Derby Query Plan Screen Shot 2.jpg,
> DERBY-4587-tool-2.diff, DERBY-4587-tool-3.diff, DERBY-4587-tool-4.diff,
> DERBY-4587-tool.diff, Derby_Query_Plan_Screen_Shot.jpg, PostgreSQL
> license.jpg, Read_Me.txt, screenshot-1.jpg, screenshot-2.jpg, Source.rar,
> test.xml, test4.xsl
>
>
> I think it would be great to see some work in the area of tools for helping
> with the analysis of complex query execution. Quite frequently, users of
> Derby have trouble comprehending (a) how their query is being translated
> into a query plan by the optimizer, and (b) what the execution-time resource
> usage of the various parts of the query is.
> There are low-level features in Derby which capture this information and
> record it, such as logQueryPlan, and the XPLAIN tables, but there is a lot
> of opportunity for designing higher-level tools which can process the query
> plan and execution statistics information and present it in a more
> comprehensible fashion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
