[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2086:
---------------------------------------
There is a mismatch between the infinispan logic and the infinispan configuration logic in
the container. You can get a handle to the CacheContainer service prior to configuration
of the caches. That CacheContainer is unaware it will configured asynchly by other
container threads. So if you ask for a named cache before that particular cache service
is configured you get the default one instead. I gather from all of this that they expect
you to depend on the caches and not the CacheContainer.
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