[
https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin...
]
John Muller commented on TEIID-3359:
------------------------------------
While it would break strict compliance with OData V2 & V4, I think the simplest option
would be to allow a cache hint as a ReST query parameter. This would offer even more
control over what gets cached and what doesn't; right down to the query-by-query
level. Config can still serve as the defaults for odata caching.
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)