[teiid-issues] [JBoss JIRA] Commented: (TEIID-829) revamp code table caching
[
https://jira.jboss.org/browse/TEIID-829?page=com.atlassian.jira.plugin.sy...
]
Steve Hawkins commented on TEIID-829:
-------------------------------------
changed the implementation to use a generated materialized view with a primary key instead
of a in memory hashmap. while the resulting table is persistent, all pages of the table
have a preference to stay in memory. I removed the configuration items related to code
tables, but it may be good to bring back an allowable max, since the number that can be
created is fairly high (the worst case is every pairing of columns from a table or view
where the key column is unique).
It's still pending to add a warning when a code table is created off of
non-deterministic values and control of purging.
revamp code table caching
-------------------------
Key: TEIID-829
URL: https://jira.jboss.org/browse/TEIID-829
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.1.1
Code tables have several design issues:
1. the cache should allow for eviction and possibly expiration.
2. the cache should be backed by the common caching facility.
3. should allow for explicit scoping - at a minimum global vs. vdb, but additional may be
good to allow session and request.
4. the implementation should be minimally blocking (in terms of both query execution and
use of synchronization).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira