[ https://issues.apache.org/jira/browse/DERBY-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681526#comment-13681526 ]
ASF subversion and git services commented on DERBY-6211: -------------------------------------------------------- Commit 1492378 from [~rhillegas] [ https://svn.apache.org/r1492378 ] DERBY-6211: Commit derby-6211-06-ab-packageProtect-XMLOptTrace.diff, reducing the visibility of XMLOptTrace. > 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 > 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 > > > 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