[teiid-issues] [JBoss JIRA] (TEIID-1598) translator scoped result set caching
[
https://issues.jboss.org/browse/TEIID-1598?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1598.
-----------------------------------
Resolution: Done
Added docs under the Developer's Guide and referenced from the Caching Guide. The 8.1
implementation does not provide any built-in caching configuration for translators, but it
would be straight-forward to create a custom delegating translator that implements a
caching policy.
Follow-on issues are:
- provide a built-in caching policy delegating translator, which could even use extension
metadata to determine what commands are cached.
- allow the translator to know the cardinality estimate for the source command
- make use of the readAll option for regular result set cache entries, which currently
don't get populated unless the entire result is constructed.
translator scoped result set caching
------------------------------------
Key: TEIID-1598
URL: https://issues.jboss.org/browse/TEIID-1598
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 8.1
Something Steven mentioned in Teiid-1589 got me thinking: It would be helpful for
individual translators to request that Teiid cache results sets that match the query as
presented to the execution factory (after the planner is done rewriting the query based on
the translator's capabilities).
I envision a new method on an Execution getCacheTtlMs() where zero or negative indicates
that Teiid shouldn't cache the results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira