]
Steven Hawkins commented on TEIID-5581:
---------------------------------------
It appears that it was only an early cs draft of the spec that specified entities with
server driven paging:
That is then echoed in microsoft and other documentation.
However later revisions switched to use the more general term items:
So the fix here should be to implement the next link over complex type collections as
well.
No @nextlink for virtualized procedure
--------------------------------------
Key: TEIID-5581
URL:
https://issues.jboss.org/browse/TEIID-5581
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.16.6_4
Reporter: Colin Mondesir
Assignee: Steven Hawkins
Priority: Major
Attachments: example.xmi, procExample_Odata_Results.xml, procExample_SELECT.sql
If we query a table "Field" via VDB, we get the following line in XML :
<a:link rel="next"
href="http://<IP-address>:8080/odata4/UDVvdb.13/BusinessObjects/Field?$skiptoken=6lS4u9tYdm4j,256"/>
This allow end-user to loop on results easily.
But when we call virtualized procedure, we do not see that line.
It looks like :
<m:value
xmlns:m="http://docs.oasis-open.org/odata/ns/metadata"
xmlns:d="http://docs.oasis-open.org/odata/ns/data"
xmlns:a="http://www.w3.org/2005/Atom"
m:type="#Collection(UDVvdb.13.Wellmap.getOffsetWells_ResultSet)"
m:context="$metadata#Collection(UDVvdb.13.Wellmap.getOffsetWells_ResultSet)">
[List of <m:element>]
</m:value>
Odata batch is currently limited to 256 so without a next link it's not possible to
get to the rest of the data.