[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2086.
-----------------------------------
Resolution: Done
This was slightly more complicated than I had hoped. In the AS environment the caches are
treated as services, not just the cache container. So without an explicit dependency on
the cache service just getting a cache from the container would automatically start a
defaultly configured cache.
So now there are explicit service dependencies and we use the embedded manager to ensure
that we don't auto create an inappropriately configured cache.
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL:
https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira