Upload one chunk of records
Stages one chunk of records against an open record set. Chunks may be sent in any order. Re-sending a chunk index that has already been received is safe: the response reports replay: true and the record set’s counters do not move.
Authorizations
Path Parameters
Body
One chunk of records for an open record set.
chunk_index is assigned by you, starting at 0, and is what makes the
upload safe to retry: re-sending the same chunk_index with the same
records is recognised as a repeat and inserts nothing, so a network failure
mid-upload is resolved by simply sending the chunk again. The response tells
you whether the chunk was new (replay: false) or already had been received
(replay: true).
A row's position in the record set is chunk_index * chunk_size + offset,
where offset is the record's position within this chunk. A short chunk in
the middle of the upload therefore leaves a gap in the numbering, which is
harmless: rows are processed by range and sealing validates the totals. If
you would rather have no gaps, send full chunks and make the last one short.
Chunks may be sent in any order, and out-of-order or retried chunks do not change the record set's content hash.
Response
Successful Response
The outcome of one chunk upload.
records_received is how many records the chunk carried and inserted is
how many of them were new. replay is true when this chunk index had
already been received, in which case inserted is normally 0 and the record
set's counters are unchanged. received_count is the record set's running
total after this chunk, which is the number to pass as expected_count when
every chunk has been sent.