[
https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-5449:
------------------------------------
In a production environment, once a cache has data, it isn't going to change without a
migration. So if a VDB has a related cache table updated, it must be backwards
compatible. Therefore, 2 simultaneous connections would not fail. However, in a
development environment, there's possibility for collisions when 2 people would be
using the same entity name.
Infinispan: Update Infinispan translator to 9.3 version
-------------------------------------------------------
Key: TEIID-5449
URL:
https://issues.jboss.org/browse/TEIID-5449
Project: Teiid
Issue Type: Bug
Components: Infinispan
Affects Versions: 11.0
Reporter: Ramesh Reddy
Assignee: Van Halbert
Priority: Major
Fix For: 11.2
Two changes observed
- The new cache create API changed, the old has been deprecated
- cache.get(key) now became Async operation, that means Thread Based serialization
context no longer works. This needs to be removed, but there seem to be no better
alternatives to support the Async threads.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)