A GemFire region is how GemFire logically groups data within its cache. Regions stores data as entries, which are key-value pairs. Using the REST APIs you can read, add (or update), and delete region data.
See also Data Regions for more information on working with regions.
List all available resources (regions) in the GemFire cluster.
Read data for the region. The optional limit URL query parameter specifies the number of values from the Region that will be returned. The default limit is 50. If the user specifies a limit of “ALL”, then all entry values for the region will be returned.
List all keys for the specified region.
Read data for a specific key in the region.
Read data for multiple keys in the region.
An HTTP HEAD request that returns region’s size (number of entries) within the HEADERS, which is a response without the content-body. Region size is specified in the pre-defined header named “Resource-Count”.
Create (put-if-absent) data in region.
Update or insert (put) data for key in region.
Update or insert (put) data for multiple keys in the region.
Update (replace) data with key(s) if and only if the key(s) exists in region. The Key(s) must be present in the Region for the update to occur.
Update (compare-and-set) value having key with a new value if and only if the “@old” value sent matches the current value having key in region.
Delete all entries in the region.
Delete entry for specified key in the region.
Delete entries for multiple keys in the region.