Avoids null values from MapLoader.load(Key)

[ramki]

Hello,

I have implemented a custom MapLoader. But, on cache miss, when load()
is called, say I cannot come up with the data with my own logic, then
I don't want the null value to go into the Map for that key. is there
any way to avoid this?

Thanks,
Ram

[Fuad Malikov]

Not right now, There is couple of issues already filed for this (566 & 578).
The reason we put null value into map is not to check the loader again with the same key. But yes, this should be transparent to the user.

Fuad

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To post to this group, send email to haze...@googlegroups.com.
To unsubscribe from this group, send email to hazelcast+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hazelcast?hl=en.

--
Fuad Malikov
+90.538.378.9777
http://twitter.com/fuadm

[ramki]

do you have any solution with existing hazelcast features? or is it up
to the the user to detect that and remove it?

[Timothy Peierls]

I'm coping with this by inverting the relationship and not using the MapLoader/MapStore functionality, instead writing Map (or Map-like) abstractions on top of a persistent store -- JClouds BlobStore, in my case -- with caching provided by Hazelcast IMaps. I store a sentinel value to represent the absence of a value in the persistent store.

This posting describes how that approach could be used in fixing MapLoader/MapStore:

https://groups.google.com/d/msg/hazelcast/-L81SCOx5UM/PAvdaixp7rcJ

--tim

[ramki]

Thanks Tim, will check it out.