[
https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3359:
---------------------------------------
I think the simplest option would be to allow a cache hint as a ReST
query parameter
Now that we have forked OData4j that may be possible, but I'm not sure how that would
work with Olingo. Perhaps just relying on something more fundamental like TEIID-3434
would work.
Allow more control over odata layer caching
-------------------------------------------
Key: TEIID-3359
URL:
https://issues.jboss.org/browse/TEIID-3359
Project: Teiid
Issue Type: Enhancement
Components: OData
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Labels: Alpha1
Fix For: 8.11
The caching is always performed at a user level and for each query. Consumers may need
to localize the caching affect only to paging results and scope only to that interaction,
rather than for all users.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)