db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics
Date Sat, 26 Jun 2010 17:02:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882858#action_12882858

Bryan Pendleton commented on DERBY-4587:

Hi Nirmal
I'm having several small problems working with the patch:
1) In my build environment, String.contains() is not available, since
I'm building with JDK 1.4, not JDK 1.5. Perhaps we could change
the contains() calls in AccessDatabase.java to use indexOf() instead?
2) It appears that the new code is not getting added to derbytools.jar.
Perhaps a build file adjustment is needed to enroll the new classes
in derbytools.jar?
3) When I run XplainStatisticsTest, I get AccessDenied exceptions
trying to write the XML files. I'm not sure exactly where the test is
trying to write these test files, but it seems the location is not acceptable to
the security policy that is getting used by the tests.

When I run the test using the 'classes' directory in my classpath, problems
(2) and (3) do not arise.

I took a quick look at the generated XML files in the output, and they
are starting to look very good!

Can we include the STATEMENT_TEXT data into the generated XML
output, so that we can see the actual statement that is getting run,
as part of the XML file?

> 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-5.diff, DERBY-4587-tool-6.diff, DERBY-4587-tool-test1.diff,
DERBY-4587-tool.diff, 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, 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.

View raw message