Transient Entries

When using a persistent space there are situations where not all the space objects need to be persistent (saved within the database). You can specify a space Object to be stored only in the space, without storing it also in the persistent store, by setting its persist mode to have a false value. You should set this value at the space class level or at the object level. When setting it at the object level you should have it set to false before writing it into the space. After the space object has been written to the space you cannot change its persist mode.

Transient Space Where GigaSpaces data is stored. It is the logical cache that holds data objects in memory and might also hold them in layered in tiering. Data is hosted from multiple SoRs, consolidated as a unified data model. 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 space object.

POJO

The following example marks an entire class transient (i.e. non-persistent):

@SpaceClass (persist=false)
public class MyData {
    ...
}

The following example marks the property which determines whether a class instance is transient or persistent:

@SpaceClass
public class MyData {
    ...
    @SpacePersist
    boolean getPersistMode()
    {
        return false;
    }
}

• Transient Space objects can be constructed using the @SpacePersist on the relevant getter method. See the GigaSpaces Data Modeling section for details.
• Transient objects will be evicted from the space only by explicit take/clear operation.
• 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.

Space Document

   SpaceDocument doc = new SpaceDocument("Entity");
   ......       
   doc.setTransient(true);