[
https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897017#action_12897017
]
Kristian Waagan commented on DERBY-4587:
----------------------------------------
I'll answer Nirmal's replies to my comments in a separate post (after having
looked into them), just want to comment on what Rick said.
Rick, you're hoping all plans go into one file. I see this as both an advantage
and a disadvantage. With the current state of the tool, I think it would be
confusing to have like 5 - 40 queries in one file.
So, here are some options I see (feel free to add your own!):
a) Everything in one file, use horizontal separators and maybe add some
navigational aids (i.e. table of contents, anchor at the top)
b) Keep each query in its own file.
c) As above, but additionally create a separate file for navigation with
(relative) links to the individual plans.
d) Add a(nother) tool to split up the single large output file.
Now, personally I would like the only requirement for the tool to be a web
browser (graphical or console based) - continuing along the lines above may
move us in the direction of a standalone tool with it's own GUI...
Another issue with selecting all available plans is security (leaking
information). How is access control currently handled by the XPLAIN
functionality?
For instance, will internal procedure queries [1] be traced as well? Can access
to those plans be limited? Does it make sense to do so?
[1] I.e., if the user does 'call myBusinessLogicProcedure', will queries issued
from inside myBusinessLogicProcedure be traced and accessible to the user
issuing the call? This isn't directly related to the PlanExporter as such, more
the XPLAIN functionality I guess.
> 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.
