Summary: How to specify that some objects in a persistent space should not be saved to persistent storage.

Overview

When using a persistent space there are situations where not all the Entries need to be stored in the persistent store. You can define the Entry to be stored only in the space cache, without storing it also in the persistent store, by setting its persistent mode to false. This setting must be specified when the Entry has been created and before it has been written to the space. After the Entry has been written to the space you cannot change its persistent mode.

Transient Space objects are treated the same as persistent objects, but when you call the write operation, only persistent objects are saved to the persistent store. All space operations, including batch operations, are valid for transient Entries.

Non-Mirrored Entries
When using the Mirror Service or the DataPersister interface, you might not want to replicate all space Entries into the mirror service to be persistent or to be delivered to some external data source.

The Mirror Service/DataPersister do not persist or deliver to external data source an Entry that has been identified as transient.

  • Transient Space objects can be constructed using the @SpacePersist on the relevant getter method. See the POJO Support - Advanced for details.
  • When the space memory usage control is turned on, a transient objects might be evicted from the space cache.
  • Having a space Class using the persist=true and memory (transient) based spaces, will not generate any errors or exceptions, but will not write these into any persistent store. The Entries will be transient.
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence