[
https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3358:
-------------------------------------
it should have been using the schema qualification for matching, if not we need to fix
that. I am under impression, Teiid did not support partial EntitySet names, it required
the fully qualified names. Looks like there is some mis-match in that case.
Issues with entity set names
----------------------------
Key: TEIID-3358
URL:
https://issues.jboss.org/browse/TEIID-3358
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
The entity set name used for sql generation should be the fully qualified name. If there
is for example two table with the same names in schemas visible to odata, but one of the
tables does not have a key, then an ambiguous name exception will be thrown if an odata
url is used with only the base table name.
It also appears that the URI link in the results metadata uses the non-qualified table
name, which will have issues in the scenario above.
We may also need to document or add an additional check for ambiguity as the OData4j
findEdmEntitySet logic will return the first matching entity, which is generally against
our approach to resolving.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)