You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to turn off the cache only for these specific dto and only in that hazelcast config,
use_second_level_cache=false or removing the cache annotation is also not the solution
(we we use the same dto class in a different contexts with multiple datasources)
@enozcan told me that eviction-size=0 ends up with Integer.MAX_VALUE.
This is not documented in any way in EvictionConfig.
Is it possible to change that and use another magic value (-1?) for unlimited size?
Or at least document this special behaviour in the javadocs?
If there is another option to turn off specific cache via hazelcast config, please let me know.
The text was updated successfully, but these errors were encountered:
qeepcologne
changed the title
HazelcastLocalCacheRegionFactory / map config / eviction size="0"
HazelcastLocalCacheRegionFactory / map config / eviction size="0" (turn off cache via hazelcast config not working)
Feb 12, 2021
qeepcologne
changed the title
HazelcastLocalCacheRegionFactory / map config / eviction size="0" (turn off cache via hazelcast config not working)
HazelcastLocalCacheRegionFactory / map config / eviction size="0" (turn off specific cache via hazelcast config not possible)
Feb 12, 2021
(summary of hazelcast/hazelcast#18158)
I am using hazelcast-hibernate53:2.2.0 with HazelcastLocalCacheRegionFactory and set config like that:
I want to turn off the cache only for these specific dto and only in that hazelcast config,
use_second_level_cache=false or removing the cache annotation is also not the solution
(we we use the same dto class in a different contexts with multiple datasources)
@enozcan told me that eviction-size=0 ends up with Integer.MAX_VALUE.
This is not documented in any way in EvictionConfig.
Is it possible to change that and use another magic value (-1?) for unlimited size?
Or at least document this special behaviour in the javadocs?
If there is another option to turn off specific cache via hazelcast config, please let me know.
The text was updated successfully, but these errors were encountered: