stage Block(String base64BlockID, Flowable<ByteBuffer> data, long length, LeaseAccessConditions leaseAccessConditions, Context context)
Uploads the specified block to the block blob's "staging area" to be later committed by a call to commitBlockList. For more information, see the Azure Docs.
Note that the data passed must be replayable if retries are enabled (the default). In other words, the
</code> must produce the same data each time it is subscribed to.</p>
public Single<BlockBlobStageBlockResponse> stageBlock(String base64BlockID, Flowable<ByteBuffer> data, long length, LeaseAccessConditions leaseAccessConditions, Context context)
A Base64 encoded
</code> that specifies the ID for this block. Note that all block ids for a given blob must be the same length. </p>
The data to write to the block. Note that this
</code> must be replayable if retries are enabled (the default). In other words, the Flowable must produce the same data each time it is subscribed to. </p>
The exact length of the data. It is important that this value match precisely the length of the data emitted by the
</code> . </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