Most appropriate place to locate the new Visualizer tool

[Nirmal Fernando <ni...@gmail.com>]

Hi All,

I need your help to find out the most appropriate place (in the Derby
folder structure) to locate the new tool, that will be developed in
this summer as the GSoC project of mine.

The Visualizer tool: Derby-4587
(https://issues.apache.org/jira/browse/DERBY-4587)

Description:

Quite frequently, users of Derby have troubles in comprehending the
steps followed by the optimizer when it translates a query into a
query plan, and details such as time to execute, resource utilization
at each step of the query plan. There are low-level features in Derby
which capture this information and record it, such as logQueryPlan,
and the XPLAIN tables, so this project will lead to a development of a
new tool which can process the query plan and execution statistics
information and present it in a more comprehensible fashion i.e. a
graphical interpretation of the query plan.

You can find information about the design at
http://wiki.apache.org/db-derby/Nirmal/Derby-4587-%20Design%20Details

Your suggestions are highly appreciated.

Thank you very much.


-- 
Best Regards,
Nirmal

C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.

Re: Most appropriate place to locate the new Visualizer tool

[Bryan Pendleton <bp...@gmail.com>]

On 05/24/2010 08:15 PM, Nirmal Fernando wrote:
> new tool which can process the query plan and execution statistics
> information and present it in a more comprehensible fashion i.e. a
> graphical interpretation of the query plan.

Hi Nirmal,

I think we should organize the new tool in a fashion similar to the
existing 'ij', 'sysinfo', and 'dblook' tools. That is, as a standalone
Java program whose main class lives in org.apache.derby.tools.exportQueryPlan
in the 'java/tools' hierarchy, and whose supplemental internal classes,
if any, live in org.apache.derby.impl.tools.exportqueryplan.*

I'm hoping the community has suggestions about the name of the
tool, as 'exportQueryPlan' is perhaps a bit awkward and verbose.

The other part of the proposed tool is an XSL stylesheet. This tool
could be stored in our source tree in a variety of possible locations,
and distributed in our releases in a variety of possible locations,
and nothing yet has jumped out to me as an obvious choice for that.

I think that for the XSL stylesheet, we should perhaps create a new
directory in the source tree: java/tools/exportQueryPlan, and store
the XSL stylesheet there.

What do others think?

thanks,

bryan