[
https://issues.jboss.org/browse/TEIID-4603?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-4603:
------------------------------------
Part of the challenge is:
- Searching is done by using the DSL query language that performs the search by object
type
- Insert/Update/Delete is done by put/remove from the map by the key
example of the issue:
- pojo A exist in the cache with key '1'.
- Insert is going to performed for pojo B with key '1'.
So when doing an insert for pojo 'B' key '1', a search is done and no
object is returned for that type, so the the insert is performed. When pojo B is inserted
with key '1', it will overlay pojo A with key '1'. Doing a search for
pojo A will no longer return a row.
One thought is to do a cache.get(key) lookup on the cache to see if any existing object is
there, instead of using the DSL searching.
Insert issue when cache contains multiple pojo's with the same
key value
------------------------------------------------------------------------
Key: TEIID-4603
URL:
https://issues.jboss.org/browse/TEIID-4603
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 9.2
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Blocker
Fix For: 9.2, 8.12.8.6_3
There is an INSERT issue when there are multiple pojo's stored in the same cache and
the keys' overlap (meaning the different types of pojo's have the same key).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)