I have a CacheStore that loads missing data from the underlying data source (an Oracle DB). At present, multiple requests for the same key will cause multiple loads from that Oracle DB, until the object is inserted in to the memory cache by Ignite.
Is there currently any way to queue up subsequent requests for a CacheStore load() that is "in flight", and then signal them all when the data is available in the memory cache? I can simulate this in my CacheStore implementation using a piece of shared context and some retry loops, but is there a native Ignite way? If not, would anyone be interested in me implementing this inside Ignite? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-servicing-multiple-requests-for-same-key-tp1589.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
