OptionalretryConfig: RetryConfigThe record(s) to append
Optionalargs: Omit<AppendArgs, "records">Optional append arguments (fencing_token, match_seq_num)
Optionaloptions: S2RequestOptionsOptional request options
Create an append session that guarantees ordering of submissions.
Use this to coordinate high-throughput, sequential appends with backpressure. Records can be either string or bytes format - the format is specified in each record.
OptionalsessionOptions: AppendSessionOptionsOptions that control append session behavior
OptionalrequestOptions: S2RequestOptionsOptional request options
Check the tail of the stream.
Returns the next sequence number and timestamp to be assigned (tail).
Optionaloptions: S2RequestOptionsRead records from the stream.
as: "bytes" is provided, bodies and headers are decoded from base64 to Uint8Array.seq_num, timestamp, or tail_offset and can clamp to the tail.count and bytes (defaults 1000 and 1 MiB).readSession for streaming readsOptionalargs: ReadArgs<Format>Optionaloptions: S2RequestOptionsOpen a streaming read session
Use the returned session as an async iterable or as a readable stream.
When as: "bytes" is provided, bodies and headers are decoded to Uint8Array.
Optionalargs: ReadArgs<Format>Optionaloptions: S2RequestOptions
Append one or more records to the stream.
fencing_tokenandmatch_seq_num.All records in a single append call must use the same format (either all string or all bytes). For high-throughput sequential appends, use
appendSession()instead.