[
https://issues.jboss.org/browse/TEIID-5581?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5581:
---------------------------------------
For a procedure that returns multiple rows we use a complex type result - but we still
apply the batch size when doing the result fetching. The skip token only affects entity
set results.
Workaround:
Add a procedure relational view with a primary key:
{code}
create view procView (Param1, myValue primary key) as select Param1, myValue from
procExample
{code}
Of course just a get of the procView entity without specifying param1 would fail.
Possible changes:
* give the user the option of specifying the procedure result as an entity - extension
metadata for the unique key?
* make the complex type procedure result unaffected by the batch size - however some cap
would still need to exist.
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)