The Append Block operation commits a new block of data to the end of an existing append blob.
Append Block operation is permitted only if the blob was created with
x-ms-blob-type set to
Append Block is supported only on version 2015-02-21 version or later.
The Append Block request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account:
|PUT Method Request URI||HTTP Version|
When making a request against the emulated storage service, specify the emulator hostname and Blob service port as
127.0.0.1:10000, followed by the emulated storage account name:
|PUT Method Request URI||HTTP Version|
For more information, see Using the Azure Storage Emulator for Development and Testing.
|timeout||Optional. The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Blob Service Operations.|
The following table describes required and optional request headers.
||Required. Specifies the authentication scheme, account name, and signature. See Authentication for the Azure Storage Services for more information.|
||Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authentication for the Azure Storage Services.|
||Required for all authenticated requests. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage Services.|
||Required. The length of the block content in bytes. The block must be less than or equal to 4 MB in size.
When the length is not provided, the operation will fail with the status code 411 (Length Required).
||Optional. An MD5 hash of the block content. This hash is used to verify the integrity of the block during transport. When this header is specified, the storage service compares the hash of the content that has arrived with this header value.
Note that this MD5 hash is not stored with the blob.
If the two hashes do not match, the operation will fail with error code 400 (Bad Request).
||Required if the blob has an active lease. To perform this operation on a blob with an active lease, specify the valid lease ID for this header.|
||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.|
||Optional conditional header. The max length in bytes permitted for the append blob. If the
||Optional conditional header, used only for the
This operation supports the use of additional conditional headers to ensure that the API succeeds only if a specified condition is met. For more information, see Specifying Conditional Headers for Blob Service Operations.
The request body contains the content of the block.
Request Syntax: PUT https://myaccount.blob.core.windows.net/mycontainer/myblob?comp=appendblock HTTP/1.1 Request Headers: x-ms-version: 2015-02-21 x-ms-date: <date> x-ms-blob-condition-appendpos: 2097152 x-ms-blob-condition-maxsize: 4194304 Authorization: SharedKey myaccount:J4ma1VuFnlJ7yfk/Gu1GxzbfdJloYmBPWlfhZ/xn7GI= Content-Length: 1048 If-Match: "0x8CB172A360EC34B"
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 201 (Created).
For information about status codes, see Status and Error Codes.
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.
|Etag||The ETag contains a value in quotes that the client can use to perform conditional PUT operations by using the If-Match request header.|
|Last-Modified||The date/time that the blob was last modified. The date format follows RFC 1123. For more information, see Representation of Date-Time Values in Headers.
Any write operation on the blob (including updates on the blob's metadata or properties) changes the last-modified time of the blob.
|Content-MD5||This header is returned so that the client can check for message content integrity. The value of this header is computed by the Blob service; it is not necessarily the same value specified in the request headers.|
|x-ms-request-id||This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations.|
|x-ms-version||Indicates the version of the Blob service used to execute the request. This header is returned for requests made against version 2009-09-19 and later.|
|Date||A UTC date/time value generated by the service that indicates the time at which the response was initiated.|
|x-ms-blob-append-offset||This response header is returned only for append operations. It returns the offset at which the block was committed, in bytes.|
|x-ms-blob-committed-block-count||The number of committed blocks present in the blob. This can be used to control how many more appends can be done.|
||Version 2015-12-11 or newer. The value of this header is set to
Response Status: HTTP/1.1 201 Created Response Headers: Transfer-Encoding: chunked Content-MD5: BN3lsXf+t19nMGs+vYakPA== Date: <date> Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0 x-ms-blob-append-offset: 2097152 x-ms-blob-committed–block-count: 1000
This operation can be called by the account owner and by anyone with a Shared Access Signature that has permission to write to this blob or its container.
Append Block uploads a block to the end of an existing append blob. The block of data is immediately available once the call succeeds on the server. A block may be up to 4 MB in size.
Append Block succeeds only if the blob already exists.
Blobs uploaded using
Append Block do not expose block ids, so you cannot call Get Block List against an append blob. Doing so results in a 409 error.
The following optional conditional headers can be specified on the request:
x-ms-blob-condition-appendpos: You can set this header to a byte offset at which the client expects to append the block. The request succeeds only if the current offset matches that specified by the client. Otherwise, the request fails with the AppendPositionConditionNotMet error (HTTP status code 412 – Precondition Failed).
Clients using a single writer may use this header to determine whether when an Append Block operation succeeded despite network failure.
x-ms-blob-condition-maxsize: Clients can use this header to ensure that append operations do not increase the blob size beyond an expected maximum size in bytes. If the condition fails, the request will fail with MaxBlobSizeConditionNotMet error (HTTP status code 412 – Precondition Failed).
Each block can be a different size, up to a maximum of 4 MB. A maximum of 50,000 appends are permitted for each append blob. The maximum size of an append blob is therefore slightly more than 195 GB (4 MB X 50,000 blocks). If you attempt to upload a block that is larger than 4 MB, the service returns HTTP status code 413 (Request Entity Too Large). The service also returns additional information about the error in the response, including the maximum block size permitted in bytes. If you attempt to upload more than 50,000 blocks, the service returns the BlockCountExceedsLimit error (HTTP status code 409 – Conflict).
If the blob has an active lease, the client must specify a valid lease ID on the request in order to write a block to the blob. If the client does not specify a lease ID, or specifies an invalid lease ID, the Blob service returns status code 412 (Precondition Failed). If the client specifies a lease ID but the blob does not have an active lease, the Blob service also returns status code 412 (Precondition Failed).
Calling Append Block on an existing block blob or page blob will return an InvalidBlobType error (HTTP status code 409 - Conflict). Calling Append Block on a non-existent blob will return a BlobNotFound error (HTTP status code 404 – Not Found).
Avoiding duplicate or delayed appends
In a single writer scenario, the client can avoid duplicate appends or delayed writes either by using the x-ms-blob-condition-appendpos conditional header to check the current offset, or by checking the ETag conditionally using
In a multiple writer scenario, each client can use conditional headers, but this may not be an optimal approach in terms of performance. For the highest concurrent append throughput, applications should handle redundant appends and delayed appends in their application layer (e.g., add epochs or sequence numbers in the data being appended).