ID Queries

The space can be queried for entries using Template Matching or SQLQuery, but sometimes we know the exact id of the entry we need and prefer a faster solution. This is where id-based queries come handy.

Reading an Entry By ID

When you would like to access an object using its ID for read and take operations you should first specify the ID field. You can specify it via [SpaceId (autogenerate=false)] annotation:

[SpaceId (autoGenerate=false)]
public String getEmployeeID() {
    return employeeID;

To read the object back from the space using its ID and the ReadById operation:

GigaSpace gigaSpace;
Employee myEmployee = proxy.ReadById<Employee>(myEmployeeID , routingValue);

Reading Multiple Entries by IDs

The following shows how to read multiple objects using their IDs:

GigaSpace gigaSpace;

// Initialize an ids array
long?[] ids = new long?[] { ... };

// Set a routingClosed The mechanism that is in charge of routing the objects into and out of the corresponding partitions. The routing is based on a designated attribute inside the objects that are written to the Space, called the Routing Index. key value (not mandatory but more efficient)
Integer routingKey = ...;

// Read objects from space
ReadByIdsResult<Employee> result = proxy.ReadByIds<Employee>( ids, routingKey);

// Loop through results
for (Employee employee : result) {
  // ...

See Parent Child Relationship for a full usage example of the readByIds operation. ReadById is intended to objects with meaningful ids,if used with auto-generate="true" ids,the given object type will be ignored.