db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6211) Make Optimizer trace logic pluggable.
Date Fri, 28 Jun 2013 12:18:21 GMT

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

Rick Hillegas commented on DERBY-6211:
--------------------------------------

Hi Bryan,

I'm not quite ready to write regression tests for xml-based optimizer tracing. I apologize
that this creates more gaps for the code-coverage project. I have at least one more change
to make to the xml output before I add some tests.

Right now I'm working on adding compact optimizer overrides for complete query plans (DERBY-6267).
The idea is that the plan summaries output by xml-based optimizer tracing will work as plan
descriptions in optimizer overrides. I've made a lot of progress on DERBY-6267 and may have
a patch to show the community in a couple days.

Until then, I want to hold off writing tests for xml-based optimizer tracing, just in case
the format of the plan summaries changes. For the same reason, I've been holding off writing
tests for xml-based execution plans (DERBY-6266). I want to use those ResultSet summaries
in the tests which verify the work on DERBY-6267. And there's a possibility that the ResultSet
summaries may have to change a bit in order to serve that purpose.

Thanks,
-Rick
                
> Make Optimizer trace logic pluggable.
> -------------------------------------
>
>                 Key: DERBY-6211
>                 URL: https://issues.apache.org/jira/browse/DERBY-6211
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>              Labels: derby_triage10_11
>         Attachments: derby-6211-01-aa-createPlugin.diff, derby-6211-02-aa-cleanup.diff,
derby-6211-02-ab-cleanup.diff, derby-6211-03-aa-customTracer.diff, derby-6211-04-aa-moveOptimizerTracerToEngineJar.diff,
derby-6211-05-aa-xmlOptimizerTracer.diff, derby-6211-06-ab-packageProtect-XMLOptTrace.diff,
derby-6211-07-aa-useSchemaQualifiedNamesInSummaries.diff, derby-6211-07-ab-useSchemaQualifiedNamesInSummaries.diff,
derby-6211-08-aa-fixNPE.diff
>
>
> Right now the trace logic in the optimizer is hard-coded to produce a stream of diagnostics.
It would be good to be able to plug alternative trace logic into the optimizer. This would
make the following possible:
> 1) Plug in trace logic which produces formats which are easier to study and which can
be analyzed mechanically. E.g., xml formatted output.
> 2) Plug in trace logic which can be used during unit testing to verify that the optimizer
has picked the right plan. Over time this might make it easier to migrate canon-based tests
to assertion-based tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message