Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5581

No @nextlink for virtualized procedure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 12.0, 11.2.2, 8.12.18.6_4
    • 8.12.16.6_4
    • OData
    • None
    • Hide

      You can reproduce by creating a View Model with a simple procedure.
      Here I created a schema named "example.xmi" with a procedure "procExample". The view is included in a vdb named datasources.

      The example schema is in attached example.xmi file
      The procExample code is in procExample_SELECT.sql file : it is an UNION of 300 harcoded value (very easy to reproduce)

      The JDBC execution "EXEC example.procExample(1)" return me 300 results as expected

      The Odata4 execution "http://<ip-address>:8080/odata4/datasources.1/example/procExample(Param1=1)" return me 256 results according to odata batch size but with no way to go to next 44 results.
      XML is in procExample_Odata_results.xml

      Show
      You can reproduce by creating a View Model with a simple procedure. Here I created a schema named "example.xmi" with a procedure "procExample". The view is included in a vdb named datasources. The example schema is in attached example.xmi file The procExample code is in procExample_SELECT.sql file : it is an UNION of 300 harcoded value (very easy to reproduce) The JDBC execution "EXEC example.procExample(1)" return me 300 results as expected The Odata4 execution "http://<ip-address>:8080/odata4/datasources.1/example/procExample(Param1=1)" return me 256 results according to odata batch size but with no way to go to next 44 results. XML is in procExample_Odata_results.xml

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. TEIID-5582 xml format option is ignored by odata crossjoin

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rhn-engineering-shawkins Steven Hawkins
              rhn-support-cmondesi Colin Mondesir
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: