commit Block List(List<String> base64BlockIDs, BlobHTTPHeaders headers, Metadata metadata, BlobAccessConditions accessConditions, Context context)
Writes a blob by specifying the list of block IDs that are to make up the blob. In order to be written as part of a blob, a block must have been successfully written to the server in a prior stageBlock operation. You can call commitBlockList to update a blob by uploading only those blocks that have changed, then committing the new and existing blocks together. Any blocks not specified in the block list and permanently deleted. For more information, see the Azure Docs.
For more efficient bulk-upload scenarios, please refer to the TransferManager for convenience methods.
public Single<BlockBlobCommitBlockListResponse> commitBlockList(List<String> base64BlockIDs, BlobHTTPHeaders headers, Metadata metadata, BlobAccessConditions accessConditions, Context context)
A list of base64 encode
</code> s that specifies the block IDs to be committed. </p>
</code> offers a means of passing arbitrary data (key/value pairs) to an <xref uid="" data-throw-if-not-resolved="false">com.microsoft.rest.v2.http.HttpPipeline</xref>'s policy objects. Most applications do not need to pass arbitrary data to the pipeline and can pass<code>Context.NONE
</code> . Each context object is immutable. The<code>withContext
</code> with data method creates a new<code>Context
</code> object that refers to its parent, forming a linked list. </p>
Emits the successful response.
It looks like the sample you are looking for has moved! Rest assured we are working on resolving this.
For more samples, please see the Samples file