[
https://issues.jboss.org/browse/TEIID-2981?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2981:
---------------------------------------
We don't even bother paginating and simply set the batch size to
2048
To follow up on that, does that mean you don't expect results greater than 2048 rows?
a generic OData cache that by default caches all results sets
smaller than some defined number would hit a greater number of ReST queries we're
actually servicing.
The initial logic will simply allow for result set caching to be enabled. If we add
additional control logic it may be around the expected size of the result set, not just
the row count, to account for varying data widths.
Add an OData query parameter that caches the resultset
------------------------------------------------------
Key: TEIID-2981
URL:
https://issues.jboss.org/browse/TEIID-2981
Project: Teiid
Issue Type: Feature Request
Components: OData
Affects Versions: 8.7
Reporter: John Muller
Assignee: Steven Hawkins
Priority: Minor
Labels: Caching, OData,
The Teiid caching guide indicates that the /*+ cache */ SQL hint is neccessary in order
to cache results [1] . We would like two features added to the OData support: (1) to
have a query parameter that basically injects the hint into the SQL statement run against
the VDB and (2) a configuration setting that turns on OData resultset caching for all
result sets smaller than some size (perhaps 256 as the default)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)