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>
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Resolved
Van Halbert <vhalbert> updated the status of jira TEIID-3553 to Reopened
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Reopened
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.
Juraj, Will need you to retest in CR2.
You're right, no CR2, yet. I'll set back to modify and will change once the CR2 build is done.
Steven Hawkins <shawkins> updated the status of jira TEIID-3553 to Closed