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

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-3358.
---------------------------------
        Labels: Alpha1  (was: )
    Resolution: Done


OData4J is now FORKed - [https://github.com/teiid/oreva], I renamed the project as "OREVA" see the reasoning behind it on the Git repo's Readme.md file. I also did a NON-SNAPSHOT release of "0.8.0" based on the forked code. OReva is currently under Teiid organization, but if there is any external community interest, I will consider moving it to its own repository.

Teiid has been rewired to use OReva, and added enhancement required for this JIRA. 

> 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: Ramesh Reddy
>              Labels: Alpha1
>             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)