This is a simple example that illustrates how to colocate the data of two VMware GemFire regions.
By default, GemFire selects the data locations for a partitioned region independent of the data locations for any other partitioned region using a hashing policy on the key. This example shows how to modify this policy in order to store related data from two regions (orderand customer) in the same member.
order
customer
customer region stores Customer objects using an int as key:
Customer
int
Region<Integer, Customer> customerRegion
order region stores Order object using an OrderKey object as key:
Order
OrderKey
Region<OrderKey, Order> accountRegion
In order to store Order objects in the same member than their related customer info, a custom partition-resolved is needed: OrderPartitionResolved. When this partition resolver receives an OrderKey object, it returns the same key (the customer id) that was used to store the related customer. In this way, GemFire applies the hashing policy over the same key for Orderand Customer related objects and as a consequence, they are stored in the same member.
OrderPartitionResolved
From the gemfire-examples/colocation directory, build the example.
gemfire-examples/colocation
$ ../gradlew build
Next start a locator, start two servers, create customer region, and create orderregion colocated with customer region.
$ ../gradlew start
Run the example to put entries into both regions.
$ ../gradlew run
Shut down the system.
$ ../gradlew stop
To prevent this message from showing again, please enable pop-up blockers for support.broadcom.com or click Continue to proceed.
