[teiid-issues] [JBoss JIRA] (TEIID-3358) Issues with entity set names

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045720#comment-13045720 ] 

Steven Hawkins commented on TEIID-3358:
---------------------------------------

OData supports fully qualified or just the last name part.  If just the last name part, the first matching will be returned - no ambiguous exceptions.

It's fairly straightforward to address using fully qualified names in the generated queries, but the link uri is filled in by OData4J - and it does not consider the entity set type full name. 

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