[
https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896982#action_12896982
]
C.S. Nirmal J. Fernando commented on DERBY-4587:
------------------------------------------------
Hi Rick,
Thanks for your feedback.
1) I'll modify the arguments, in my next patch.
2) Don't you think that a user will dislike when plans for all the tracked
statements get generated each and every time he executed the tool? It may take
considerable amount of time given that there are lots of tracked queries. Also
we may get into trouble when naming the generated files. What do you think?
3) Pardon me about the comment, as I said my above reply to Kristian I'll
modify it to "Apache Derby Query Explainer (DERBY-4587)" in my next patch.
PS: I suspect that the tool does not need Xalan.jar in the CLASSPATH, both to
pass tests and generate query plans. Instead it uses the inbuilt Xalan classes
in java. Can you please verify this, if you got some time?
Thanks.
> 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: AdavancedXSL-mouseover.jpg, advancedViewXSL.xsl,
> advancedViewXSL.xsl, advancedViewXSL2.xsl, advancedXSL-1.jpg,
> advancedXSL-2.jpg, advancedXSL-3.jpg, basic_html-2.2.jpg, basic_html-2.3.jpg,
> basic_html-2.jpg, basic_html-3.jpg, basic_html-4.1.jpg, basic_html-4.2.jpg,
> Derby Query Plan Screen Shot 2.jpg, DERBY-4587-javadoc_fix.diff,
> DERBY-4587-tool-2.diff, DERBY-4587-tool-3.diff, DERBY-4587-tool-4.diff,
> DERBY-4587-tool-5.diff, DERBY-4587-tool-6.diff, DERBY-4587-tool-7-b.diff,
> DERBY-4587-tool-7.diff, DERBY-4587-tool-8.diff, DERBY-4587-tool-9.1.diff,
> DERBY-4587-tool-9.2.diff, DERBY-4587-tool-9.3.diff, DERBY-4587-tool-9.4.diff,
> DERBY-4587-tool-9.5.diff, DERBY-4587-tool-9.6.diff, DERBY-4587-tool-9.7.diff,
> DERBY-4587-tool-9.7.diff, DERBY-4587-tool-9.diff, DERBY-4587-tool-test1.diff,
> DERBY-4587-tool-test2.diff, DERBY-4587-tool.diff, derby-logo.png,
> Derby_Query_Plan_Screen_Shot.jpg, PostgreSQL license.jpg, Read_Me.txt,
> screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, Simple HTML View (Pure
> XSL).jpg, Source.rar, test.xml, test4.xsl, vanilla_html.xsl,
> vanilla_html.xsl, vanilla_html.xsl, vanilla_html.xsl, vanilla_html.xsl,
> xml_doc_screenshot.jpg, xml_doc_screenshot.jpg
>
>
> 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.
