Overview

• An Entry must be constructed using the ClientUIDHandler to have the Entry UID created prior writing it into the space - the UID should correspond to the primary key - the first defined index field toString() value. Either have __setEntryUid() and __getEntryUid() methods implemented, or extend your class from IMetaDataEntry and provide the UID as part of EntryInfo object using the MetaDataEntry.__setEntryInfo method.
• When using the Map API, the class value must have the gs.xml with converter-type=map.
• Map API is bound to only one POJO mapping, which is defined by the <entity-class> tag in space schema.
• Versioning is not supported - optimistic locking mode is not supported.
• Null as template value is not supported. This means you cannot have the following call:

  MyPOJOClass myObject = (MyPOJOClass)space.read((Object)null , null , 0)

• The Count operation takes data within the space into consideration.
• Native Serialization should be used.
• The following limitations exist for the Mirror Service:
  • Mirror - only one per cluster.
  • The Mirror service cannot be a clustered space.
  • Memory cannot be recovered when using the Mirror Service.
  • The Mirror service cannot be used with a single space or the partitioned cluster schema. It is supported with the sync-replicated, async-replicated, and partitioned-sync2backup cluster schemas.
• engine.initial_load should be configured with a small number, to avoid memory shortage in persistent spaces with large data.
• Partitioned schema should not have the failover policy or the failover policy-type set to fail-to-backup.
• RegExQuery is not supported by the CacheLoader.
• No Lease renewal or less different than Lease.FOREVER. You may use only Lease.FOREVER.
• When using Map API, key must be Serializable.
• Lazy load is not supported.