Merge Entity operation updates an existing entity by updating the entity's properties. This operation does not replace the existing entity, as the Update Entity operation does.
Merge Entity request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account,
mytable with the name of your table, and myPartitionKey and myRowKey with the name of the partition key and row key identifying the entity to be updated:
|Method||Request URI||HTTP Version|
The address of the entity to be updated may take a number of forms on the request URI. See the OData Protocol for additional details.
Emulated storage Service URI
When making a request against the emulated storage service, specify the emulator hostname and Table service port as
127.0.0.1:10002, followed by the emulated storage account name:
|Method||Request URI||HTTP Version|
The Table service in the storage emulator differs from the Windows® Azure™ Table service in several ways. For more information, see Differences Between the Storage Emulator and Azure Storage Services.
The following additional parameters may be specified on the request URI.
||Optional. The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Table Service Operations.|
The following table describes required and optional request headers.
||Required. Specifies the authorization scheme, account name, and signature. For more information, see Authorize requests to Azure Storage.|
||Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authorize requests to Azure Storage.|
||Optional. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage Services.|
||Required. Specifies the content type of the payload. Possible values are
For more information about valid content types, see Payload Format for Table Service Operations.
||Required. The length of the request body.|
||Required. The client may specify the ETag for the entity on the request in order to compare to the ETag maintained by the service for the purpose of optimistic concurrency. The update operation will be performed only if the ETag sent by the client matches the value maintained by the server, indicating that the entity has not been modified since it was retrieved by the client.
To force an unconditional update, set
||Optional. Provides a client-generated, opaque value with a 1 KB character limit that is recorded in the analytics logs when storage analytics logging is enabled. Using this header is highly recommended for correlating client-side activities with requests received by the server. For more information, see About Storage Analytics Logging and Azure Logging: Using Logs to Track Storage Requests.|
Merge Entity operation sends the entity to be updated as an OData entity, which may be either a JSON or an Atom feed. For more information, see Inserting and Updating Entities.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 204 (No Content).
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
||The ETag for the entity.|
||This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations.|
||Indicates the version of the Table service used to execute the request. This header is returned for requests made against version 2009-09-19 and later.|
||A UTC date/time value generated by the service that indicates the time at which the response was initiated.|
||This header can be used to troubleshoot requests and corresponding responses. The value of this header is equal to the value of the
Response Status: HTTP/1.1 204 No Content Response Headers: Connection: Keep-Alive Content-Length: 0 Cache-Control: no-cache Date: Mon, 25 Nov 2013 19:06:47 GMT ETag: W/"0x5B168C7B6E589D2" x-ms-version: 2013-08-15 DataServiceVersion: 1.0;NetFx MaxDataServiceVersion: 2.0;NetFx Server: Windows-Azure-Table/1.0 Microsoft-HTTPAPI/2.0
This operation can be performed by the account owner and by anyone with a shared access signature that has permission to perform this operation.
The Table service does not persist
null values for properties. Specifying a property with a
null value is equivalent to omitting that property in the request. Only properties with non-
null values will be updated by the
Merge Entity operation.
A property cannot be removed with a
Merge Entity operation. To remove a property from an entity, replace the entity by calling the Update Entity operation.
When merging an entity, you must specify the
RowKey system properties as part of the merge operation.
An entity's ETag provides default optimistic concurrency for merge operations. The ETag value is opaque and should not be read or relied upon. Before a merge operation occurs, the Table service verifies that the entity's current ETag value is identical to the ETag value included with the request in the
If-Match header. If the values are identical, the Table service determines that the entity has not been modified since it was retrieved, and the merge operation proceeds.
If the entity's ETag differs from that specified with the merge request, the merge operation fails with status code 412 (Precondition Failed). This error indicates that the entity has been changed on the server since it was retrieved. To resolve this error, retrieve the entity again and reissue the request.
To force an unconditional merge operation, set the value of the
If-Match header to the wildcard character (*) on the request. Passing this value to the operation will override the default optimistic concurrency and ignore any mismatch in ETag values.
If-Match header is missing from the request in versions 2011-08-18 and later, then the service performs an Insert Or Merge Entity (upsert) operation. In versions prior to 2011-08-18, the service returns status code 400 (Bad Request).
Any application that can authorize and send an HTTP MERGE request can merge an entity. For more information about constructing a query by using HTTP MERGE, see How to: Add, Modify, and Delete Entities.
For information about performing batch merge operations, see Performing Entity Group Transactions.