I’m sure there are lots of patterns that could be used for this. Here’s one idea: create a third region with a key that points to the region with the current data. Use a CQ or subscription or poll to get the key pointing to the region with current data. Update the reference key to point to the other region after the data load is done.
Anthony > On Sep 26, 2018, at 1:40 AM, aashish choudhary <[email protected]> > wrote: > > Use case description:- > > We have requirement where in we will have two geode regions let's say > position1 and position2 now position1 will have positions as of 25 september > after end of the day a data load operation will run which will put data to > position2 region. At this point while data load is running any get request > will be served from position1 region because there is a possibility of > getting stale data. Now the client will have to make a switch to position2 > region to serve get request with latest data after the load gets completed. > So is there any way by which a client application could make a switch to > different region once the data load gets completed . > > > With best regards, > Ashish
