The base implementation for a destination that allows writing of data in a stream.

Use this to pass your AzureBlobStorage connection information. There are different methods to connect with Azure Blob Storage: Option 1: provide an existing BlockBlobClient Option 2: create BlockBlobClient based on the Uri and optional credential tokens - the Uri needs to be the blob url Option 3: create BlobkBlobClient with provided ConnectionString and ContainerName, the Uri is then the name of the blob

By default, stream are created internally based on Uri & ResourceType. If you already have an existing stream, use this function to returns a new StreamWriter based on this stream.

Encoding used to write data into the source file or web request.

This function returns the next url that is used for writing data. It will used until HasNextUri returns false. The incoming StreamMetaData holds information about the current progress and currently processed data row. This property can be used if you want to write into multiple files or send data into different web services.

This func determines if the next data record should be written into another location. StreamMetaData has information about the current progress and currently processed data row.

The System.Net.HttpClient used to connect with the destination (only needed when the ResourceType is Http.

The content type used when sending the http request content.

The System.Net.Http.HttpRequestMessage used for the request in the HttpClient. Use this property to add additional header data type or to change the http method (e.g. for POST requests).

The System.Net.HttpResponseMessage returned from the current request. The response message is avaiable after all data rows were sent to the destination.

Specifies the resource type. Use ResourceType.File if you want to write into a file (default) Use ResourceType.Http to write into a web endpoint.

The stream writer used for the current request.

The Url of the webservice (e.g. https://test.com/foo) or the file name (relative or absolute)

The Uri used for the current write operation- this will only be different to the Uri if you use the GetNextUri and HasNextUri functions.