[
https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2519:
-------------------------------------
Sorry, Devin. It is my mistake, I forgot to make note in the document about below.
Since OData URL structure is dependent upon key structure, every table it exposes MUST
either have a primary or unique key, otherwise they will be skipped during the metadata
load. If the server is running in the DEBUG mode you would have seen a message in the log.
When I was testing it, I used other VDB, it happens to be when I used the 8.3 Final I used
the loopy VDB I supplied before and saw the behavior and thought it was a regression,
however it is not, it is designed to work that way.
So, make sure your tables have a PRIMARY KEY, and they will work. I will update the
document with this info.
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/refinedSalar...
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