[jira] [Created] (TRAFODION-895) LP Bug: 1411355 - User-level CQDs also seem to apply to metadata queries

["Alice Chen (JIRA)" <ji...@apache.org>]

Alice Chen created TRAFODION-895:
------------------------------------

             Summary: LP Bug: 1411355 - User-level CQDs also seem to apply to metadata queries
                 Key: TRAFODION-895
                 URL: https://issues.apache.org/jira/browse/TRAFODION-895
             Project: Apache Trafodion
          Issue Type: Bug
          Components: sql-cmp
            Reporter: Hans Zeller
            Assignee: justin.du@hp.com


Prashanth found this issue while fixing LP bug 1395233.

The fix turns CQDs MERGE_JOINS and HASH_JOINS off for a couple of metadata queries.
We have a regression test that sets CQD OPTIMIZATION_LEVEL to minimum. That test failed, because the metadata query did not produce a plan. It seems like the OPTIMIZATION_LEVEL CQD also applies to metadata queries.

This is the log that Prashanth got:

[/opt/home/vasudevp/traf/core/sql/sqlcomp ]sqlci
Trafodion Conversational Interface 0.9.1
(c) Copyright 2014 Hewlett-Packard Development Company, LP.
>>control query default optimization_level '0';

--- SQL operation complete.
>>prepare xx from SELECT * FROM trafodion.sch.svsel16  BROWSE ACCESS ;

*** ERROR[4082] Object TRAFODION.SCH.SVSEL16 does not exist or is inaccessible.

*** ERROR[8822] The statement was not prepared.

>>control query default optimization_level reset;

--- SQL operation complete.
>>prepare xx from SELECT * FROM trafodion.sch.svsel16  BROWSE ACCESS ;

--- SQL command prepared.
>>


There are probably two things we should fix: First, we should not apply user-level CQDs to our metadata queries, that could cause all kinds of trouble. Second, when hash joins and merge joins are turned off and the optimization level is minimum, we should still be able to produce a plan, probably by ignoring one of these CQDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)