You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "David Wayne Birdsall (JIRA)" <ji...@apache.org> on 2017/10/05 00:16:00 UTC

[jira] [Created] (TRAFODION-2765) MDAM is not considered when sometimes it should be

David Wayne Birdsall created TRAFODION-2765:
-----------------------------------------------

             Summary: MDAM is not considered when sometimes it should be
                 Key: TRAFODION-2765
                 URL: https://issues.apache.org/jira/browse/TRAFODION-2765
             Project: Apache Trafodion
          Issue Type: Bug
          Components: sql-cmp
    Affects Versions: 2.3-incubating
         Environment: All
            Reporter: David Wayne Birdsall
            Assignee: David Wayne Birdsall


The Optimizer has logic in method ScanOptimizer::useSimpleFileScanOptimizer that tries to determine scenarios where a single subset access will clearly be optimal, and in those scenarios does not consider MDAM. An example would be a query whose only key predicates are equality predicates on a leading subset of the key columns.

However, the logic in ScanOptimizer::useSimpleFileScanOptimizer sometimes rules out considering MDAM when it would be beneficial to do so. An example is a query with equality predicates on the first two columns of the key, no predicates on the third, and equality on the fourth. When the UEC of the third column is small, MDAM is likely to be the more efficient plan and should be considered.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)