[teiid-issues] [JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-2519:
-------------------------------------

I went back and tested with Teiid 8.3.Beta3 it works, with Final I see the behavior you are seeing. Seems like a regression, not sure what that is yet?

I tried with 8.4.CR1 it works as expected, can you test/move to the latest and make sure it works for your usecase before 8.4 Final?
                
> Odata Table Query Not Workng
> ----------------------------
>
>                 Key: TEIID-2519
>                 URL: https://issues.jboss.org/browse/TEIID-2519
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 8.3
>         Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3.
>            Reporter: devin pinkston
>            Assignee: Ramesh Reddy
>            Priority: Minor
>              Labels: odata,, service,, web
>             Fix For: 8.4
>
>         Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml
>
>
> When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found
> When issuing the query:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries
> We have also tried using:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries
> When issuing the second query, this error is thrown:
> <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error>
> We can successfully display the metadata and see the details of the VDB by using:
> http://localhost:8080/odata/Portfolio.1/$metadata
> Please let me know if you need any more information

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira