ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlekshma <muthu.kumara...@gmail.com>
Subject MyBatis Ignite L2 cache Integration issues
Date Tue, 06 Jun 2017 00:06:29 GMT
Hi Folks,

I see the following issues when using mybatis-ignite. Wondering if any one
else faced & solved these issues or if i am missing something as these seem
very difficult to work around,

1. Eviction or flushing of all entries on insert : Basically whenever i call
a mapper.insert operation all current entries in the cache get flushed. I
guess i can set the flushCache to false and in the code follow up the insert
with a get by that id to make sure it gets cached..but i am wondering if
this is something that can be fixed or if i am doing something wrong.

2. No caching on insert : As mentioned earlier, in addition to flushing of
all entries the entry being inserted with mapper.insert is also not getting
cached by default which again can be worked around by the above method.

3. No caching when using selectByExample (to select based on a condition or
to select all entries) & select by a CustomCriteria (using Criteria Object)
: Basically when using mapper.selectByExample instead of selectByPrimaryKey
or when selecting with a custom criteria object, the fetched entities don't
get cached. I am not sure how i can work around this issue. This is also a
bit of a problem since on app restarts we will need the cache to be loaded
with all entries in the DB table by virtue of doing a
mapper.selectByExample.

Thanks
Muthu



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-issues-tp13391.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message