With the Upsert method, Context Store either updates an existing context with new data or creates a new context if it does not exist in the data grid. Combining the two operations into a single request reduces the number of API calls.
However, due to the nature of Upsert operations, it is computationally more expensive to complete an Upsert request than to do a single create or update request.
You can perform the Upsert operations using aliasIds. You can also set the lease time of a context with the Upsert method. Context Store applies the lease time that you provide to the context in both Create and Update operations.
Certain fields of the context metadata are immutable by design. You cannot modify the immutable fields of an existing context using the Upsert method. However, if you create a new context with the Upsert method, you can define the properties for the new context .
Note:
There is a performance consideration for Upsert that should be taken into account. A single Upsert operation is more computationally expensive than its corresponding POST or PUT request and can take up to three times longer to complete. Hence, if you are using the Upsert method, the total number of requests per second supported will be reduced as per the number of the Upsert request used per second.
For detailed usage information of Upsert operation, see the Avaya Context Store Snap-in Developer Guide.
