Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 10224 invoked from network); 23 Jul 2010 17:08:13 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Jul 2010 17:08:13 -0000 Received: (qmail 8994 invoked by uid 500); 23 Jul 2010 17:08:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 8936 invoked by uid 500); 23 Jul 2010 17:08:12 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 8926 invoked by uid 99); 23 Jul 2010 17:08:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jul 2010 17:08:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jul 2010 17:08:12 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o6NH7p2A017806 for ; Fri, 23 Jul 2010 17:07:51 GMT Message-ID: <2221613.549121279904871387.JavaMail.jira@thor> Date: Fri, 23 Jul 2010 13:07:51 -0400 (EDT) From: "C.S. Nirmal J. Fernando (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics In-Reply-To: <1597970315.314791268837787263.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C.S. Nirmal J. Fernando updated DERBY-4587: ------------------------------------------- Attachment: DERBY-4587-tool-9.5.diff Hi All, Attached DERBY-4587-tool-9.5.diff. I modified tests added by me in XplainStatisticsTest class, such that they are compatible with Java-4. I ran tests and all were passed. I highly appreciate if someone (since Bryan will not be available) can apply this patch and confirm that the tests ran successfully. Thank you very much! > 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: 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-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.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.