[
https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3434:
---------------------------------------
So you are enabling result set caching then by a connection property?
We do track result set cache entries down to a table level. If the source updates are
through teiid, then the result set cache is already sensitive to those changes.
If the changes are external, then either you could look into notifying us of the change
events or as an enhancement it seems like what you are looking for is extension metadata
on the table to specify the ttl in the cache.
Individually enabling materialization can work as well.
Ability to enable/disable caching by table and/or source
--------------------------------------------------------
Key: TEIID-3434
URL:
https://issues.jboss.org/browse/TEIID-3434
Project: Teiid
Issue Type: Feature Request
Reporter: Burak Serdar
Assignee: Steven Hawkins
We need to be able to enable/disable caching by table and/or source. Some of our tables
have real-time data, and we do not want to cache those, and some other tables can use
cached data. It is not sufficient to use SQL options to turn caching on or off, because
we're using 3rd party tools, and we don't have control over the SQL they generate.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)