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] [Created] (DERBY-6211) Make Optimizer trace logic pluggable.
Date Wed, 01 May 2013 18:38:16 GMT
Rick Hillegas created DERBY-6211:
------------------------------------

             Summary: 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


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