You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/06/12 21:58:20 UTC

[jira] [Updated] (DERBY-6259) Collapse the level 2 optimizer into its parent module.

     [ https://issues.apache.org/jira/browse/DERBY-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-6259:
---------------------------------

    Attachment: derby-6259-01-aa-collapseOptimizers.diff

Attaching derby-6259-01-aa-collapseOptimizers.diff. This patch collapses the two optimizers together. I will run tests.

Touches the following files:

M       java/engine/org/apache/derby/impl/sql/compile/OptimizerFactoryImpl.java
D       java/engine/org/apache/derby/impl/sql/compile/Level2CostEstimateImpl.java
D       java/engine/org/apache/derby/impl/sql/compile/Level2OptimizerImpl.java
M       java/engine/org/apache/derby/impl/sql/compile/OptimizerImpl.java
D       java/engine/org/apache/derby/impl/sql/compile/Level2OptimizerFactoryImpl.java
M       java/engine/org/apache/derby/impl/sql/compile/CostEstimateImpl.java
M       java/engine/org/apache/derby/modules.properties
M       java/testing/org/apache/derbyTesting/functionTests/harness/Sed.java

                
> Collapse the level 2 optimizer into its parent module.
> ------------------------------------------------------
>
>                 Key: DERBY-6259
>                 URL: https://issues.apache.org/jira/browse/DERBY-6259
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6259-01-aa-collapseOptimizers.diff
>
>
> Right now there are 2 optimizer implementations, only one of which is ever loaded. The other implementation was disabled by the following comment in modules.properties:
> # use level1 optimizer for small configurations
> #
> # can't do this in the codeline because with 2 implementations, it is entirely
> # by chance which get picked.  So we may be running with different modules
> # depending on which jdk
> #
> # to be resolve by Siuling and Dan
> #
> #derby.module.optimizerSmall=org.apache.derby.impl.sql.compile.OptimizerFactoryImpl
> #cloudscape.config.optimizerSmall=cloud,cloudtarget
> Since we have deprecated support for the small CDC configuration, I don't think that we need further resolution by Siuling and Dan. Collapsing the two optimizers together should slightly reduce our static footprint.

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