FileSystemOperationsExtensions.ConcurrentAppendAsync Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Appends to the specified file, optionally first creating the file if it does not yet exist. This method supports multiple concurrent appends to the file. NOTE: The target must not contain data added by Create or normal (serial) Append. ConcurrentAppend and Append cannot be used interchangeably; once a target file has been modified using either of these append options, the other append option cannot be used on the target file. ConcurrentAppend does not guarantee order and can result in duplicated data landing in the target file.
public static System.Threading.Tasks.Task ConcurrentAppendAsync (this Microsoft.Azure.Management.DataLake.Store.IFileSystemOperations operations, string accountName, string filePath, System.IO.Stream streamContents, Microsoft.Azure.Management.DataLake.Store.Models.AppendModeType? appendMode = default, Microsoft.Azure.Management.DataLake.Store.Models.SyncFlag? syncFlag = default, System.Threading.CancellationToken cancellationToken = default);
public static System.Threading.Tasks.Task ConcurrentAppendAsync (this Microsoft.Azure.Management.DataLake.Store.IFileSystemOperations operations, string accountName, string path, System.IO.Stream streamContents, Microsoft.Azure.Management.DataLake.Store.Models.AppendModeType? appendMode = default, Microsoft.Azure.Management.DataLake.Store.Models.SyncFlag? syncFlag = default, System.Threading.CancellationToken cancellationToken = default);
static member ConcurrentAppendAsync : Microsoft.Azure.Management.DataLake.Store.IFileSystemOperations * string * string * System.IO.Stream * Nullable<Microsoft.Azure.Management.DataLake.Store.Models.AppendModeType> * Nullable<Microsoft.Azure.Management.DataLake.Store.Models.SyncFlag> * System.Threading.CancellationToken -> System.Threading.Tasks.Task
static member ConcurrentAppendAsync : Microsoft.Azure.Management.DataLake.Store.IFileSystemOperations * string * string * System.IO.Stream * Nullable<Microsoft.Azure.Management.DataLake.Store.Models.AppendModeType> * Nullable<Microsoft.Azure.Management.DataLake.Store.Models.SyncFlag> * System.Threading.CancellationToken -> System.Threading.Tasks.Task
<Extension()>
Public Function ConcurrentAppendAsync (operations As IFileSystemOperations, accountName As String, filePath As String, streamContents As Stream, Optional appendMode As Nullable(Of AppendModeType) = Nothing, Optional syncFlag As Nullable(Of SyncFlag) = Nothing, Optional cancellationToken As CancellationToken = Nothing) As Task
<Extension()>
Public Function ConcurrentAppendAsync (operations As IFileSystemOperations, accountName As String, path As String, streamContents As Stream, Optional appendMode As Nullable(Of AppendModeType) = Nothing, Optional syncFlag As Nullable(Of SyncFlag) = Nothing, Optional cancellationToken As CancellationToken = Nothing) As Task
Parameters
- operations
- IFileSystemOperations
The operations group for this extension method.
- accountName
- String
The Azure Data Lake Store account to execute filesystem operations on.
- filePathpath
- String
The Data Lake Store path (starting with '/') of the file to which to append using concurrent append.
- streamContents
- Stream
The file contents to include when appending to the file.
- appendMode
- Nullable<AppendModeType>
Indicates the concurrent append call should create the file if it doesn't exist or just open the existing file for append. Possible values include: 'autocreate'
Optionally indicates what to do after completion of the concurrent append. DATA indicates that more data will be sent immediately by the client, the file handle should remain open/locked, and file metadata (including file length, last modified time) should NOT get updated. METADATA indicates that more data will be sent immediately by the client, the file handle should remain open/locked, and file metadata should get updated. CLOSE indicates that the client is done sending data, the file handle should be closed/unlocked, and file metadata should get updated. Possible values include: 'DATA', 'METADATA', 'CLOSE'
- cancellationToken
- CancellationToken
The cancellation token.