[
https://issues.jboss.org/browse/TEIID-1598?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1598:
---------------------------------------
Sorry I wasn't clear. You have a comment on this issue above:
"I can easily imagine streaming queries that join with non-streamable result sets.
For example, suppose I want a stream of temperature readings by city but I have a set of
weather stations that report temperature by station ID and, separately, I have a mapping
table of station ID to city."
I'm saying that will be handled as part of TEIID-2077 or can just as easily be left
off as default behavior. As for the cache directive I'm mentioning here, it will be
independent of continuous queries. It will look something like
http://anonsvn.jboss.org/repos/teiid/trunk/api/src/main/java/org/teiid/tr...
The basic functioning will be to add a method on the translator to ask for a
CacheDirective for a given query prior to execution. Commands that may be in cache will
then be looked up or will have their results properly buffered for reuse. The
ExecutionContext will also be given the CacheDirective so that caching parameters can be
adjusted by the Execution for when the results have been fully read and the cache entry
created.
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