aio.ext.write¶
Async write helpers with guaranteed client-side content hashing. Async
counterpart of ext.write — same guarantees, zero extra round
trips, no buffering for async-iterator input.
See the Write Integrity guide for usage examples and the ext.write spec for invariants.
write
¶
Async write helpers with client-side content hashing.
Guarantees a populated WriteResult.digest regardless of whether the
backend declares WRITE_RESULT_NATIVE. The hash is always computed
client-side over the bytes as they flow to the backend.
write_with_hash
async
¶
write_with_hash(
store: AsyncStore,
path: str,
content: bytes | AsyncIterator[bytes],
*,
algorithm: str = "sha256",
overwrite: bool = False,
metadata: Mapping[str, str] | None = None,
) -> WriteResult
Write content and return a WriteResult with digest populated.
Hash is computed client-side as data flows to the backend -- zero extra
round trips, no buffering for async-iterator input. source is
preserved from the underlying store.write() result.
Parameters:
-
store(AsyncStore) –Target async store.
-
path(str) –Destination path.
-
content(bytes | AsyncIterator[bytes]) –bytesorAsyncIterator[bytes]. -
algorithm(str, default:'sha256') –hashlibalgorithm name. Default"sha256". -
overwrite(bool, default:False) –Same semantics as
AsyncStore.write. -
metadata(Mapping[str, str] | None, default:None) –Optional user metadata; subject to
USER_METADATAgate.
Returns:
-
WriteResult–WriteResultwithdigestpopulated from the client-side hash.