Persistent persistence

edit

Yes, so I can use the advantages of mirror service and too save forever the processed objects

U can control the space object life cycle without removing it from the database by using finite lease when writing the object to the space or when updating it (see the lease parameter). Once the space object lease will expire it will be removed from the space but will not be removed from the database (mirror will not be called). There is some known issue with this mechanism (wrong data clean up) which got simple workaround. Send me email to shay@gigaspaces.com for the exact workaround description.

In terms of loading what the space had - u will need to query database with the relevant data u want to load. This means u need to implement the EDS initialLoad method.

I presume u don't want to lazy load data from the database (LRU cache policy) but run in ALL IN CACHE policy.

Shay

Thank you so much, Shay. I kind of made the first part. Not so much documentation for the last one. I will just send you an email.

XAP 6.6.2 include a fix that resolved the leak when having a space object with finite lease when the space having EDS: http://www.gigaspaces.com/wiki/displa...

GS-6047 When writing Non-transient entries to a space with an External Data Source, the expired entries are not cleaned by the space

Shay