Bug 1234724 - Odata - if table name is ambiguous, teiid returns result from first table
Summary: Odata - if table name is ambiguous, teiid returns result from first table
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: 6.2.0
Assignee: Van Halbert
QA Contact: Juraj Duráni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-23 06:48 UTC by Juraj Duráni
Modified: 2016-02-10 08:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-10 08:50:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-3553 0 Major Closed Odata - if table name is ambiguous, teiid returns result from first table 2016-01-25 14:36:13 UTC

Description Juraj Duráni 2015-06-23 06:48:54 UTC
Describe the issue: 
If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC.


Additional information: 
URL: http://localhost:8080/odata/odata-fqn.1/smalla(0)?$format=json
VDB:
<vdb name="odata-fqn" version="1">
    <model name="Source1">
        <source name="local2" translator-name="postgresql" connection-jndi-name="java:/postgres92"/>
        <metadata type="DDL"><![CDATA[
            CREATE FOREIGN TABLE smalla (intkey integer PRIMARY KEY, stringkey string, longnum long) OPTIONS(UPDATABLE 'TRUE');
            ]]>
        </metadata>
    </model>
    <model name="Source2">
        <source name="local" translator-name="mysql5" connection-jndi-name="java:/MySQL55_PushDS"/>
        <metadata type="DDL"><![CDATA[
            CREATE FOREIGN TABLE smalla (intkey integer PRIMARY KEY, stringkey string) OPTIONS(UPDATABLE 'TRUE');
            ]]>
        </metadata>
    </model>
</vdb>

Comment 1 JBoss JIRA Server 2015-06-24 16:29:10 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Resolved

Comment 2 JBoss JIRA Server 2015-06-30 15:18:36 UTC
Van Halbert <vhalbert> updated the status of jira TEIID-3553 to Reopened

Comment 3 JBoss JIRA Server 2015-07-01 20:34:14 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Resolved

Comment 4 JBoss JIRA Server 2015-09-02 14:35:11 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Reopened

Comment 5 JBoss JIRA Server 2015-09-02 17:33:26 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Resolved

Comment 6 Van Halbert 2015-09-02 18:20:17 UTC
The engineers identified a regression with fetching nav properties in regards to the fix that was applied.  So they reopened the jira and committed a fix.

So I'm resetting this to ON-QA for revalidation to confirm no other regression is found.

Comment 7 Van Halbert 2015-09-02 18:21:20 UTC
Juraj,

Will need you to retest in CR2.

Comment 9 Van Halbert 2015-09-03 17:45:40 UTC
You're right, no CR2, yet.  I'll set back to modify and will change once the CR2 build is done.

Comment 10 JBoss JIRA Server 2015-10-30 12:49:09 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Closed


Note You need to log in before you can comment on or make changes to this bug.