[teiid-issues] [JBoss JIRA] (TEIID-2479) Selecting from SYS model throws exception

[Graeme Gillies (JIRA)]

Graeme Gillies created TEIID-2479:
-------------------------------------

             Summary: Selecting from SYS model throws exception
                 Key: TEIID-2479
                 URL: https://issues.jboss.org/browse/TEIID-2479
             Project: Teiid
          Issue Type: Bug
    Affects Versions: 8.3
         Environment: Teiid 8.3 running in JBoss EAP 6.0 RPM install

java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (rhel-2.3.8.0.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
            Reporter: Graeme Gillies
            Assignee: Steven Hawkins


We have a dynamic vdb deployed into our Teiid 8.3 environment, but whenever we connect to the vdb via the pgsql emulation socket using the standard postgresql tools, and attempt to select any value from any tables in the SYS scheama, we are given an error

{noformat}
TestVDB=> select * from sys.keys;
ERROR:  Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute
DETAIL:  org.teiid.jdbc.TeiidSQLException: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute
TestVDB=> select * from sys.columns;
ERROR:  Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute
DETAIL:  org.teiid.jdbc.TeiidSQLException: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute
TestVDB=> select * from sys.tables;
ERROR:  Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute
DETAIL:  org.teiid.jdbc.TeiidSQLException: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute
TestVDB=>
{noformat}

It looks like the teiid parser is getting confused somehow with multiple pg_attribute fields on those tables or something.

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