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 2018/02/28 16:55:00 UTC

[jira] [Resolved] (TRAFODION-2966) New MDAM costing code does not always respect CQS forcing MDAM

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

David Wayne Birdsall resolved TRAFODION-2966.
---------------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3

> New MDAM costing code does not always respect CQS forcing MDAM
> --------------------------------------------------------------
>
>                 Key: TRAFODION-2966
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2966
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-cmp
>    Affects Versions: 2.3
>            Reporter: David Wayne Birdsall
>            Assignee: David Wayne Birdsall
>            Priority: Major
>             Fix For: 2.3
>
>
> I ran the full regression suite but with CQD MDAM_COSTING_REWRITE set to 'ON' in the system defaults table. The suite passed except for test seabase/TEST010. There, several queries switched from MDAM plans to single subset scans. They did so in spite of the presence of CONTROL QUERY SHAPE statements that force an MDAM plan. So there is a bug in the new costing code where it is not respecting these CQS statements.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)