Hanzo
OpenapiDataset

Dispose of one dataset and every version of it

Disposes of one dataset and every version of it: the rows are dropped and the register is marked with what went. This is the ONLY expiry in this plane.

DELETE /v1/dataset/{name}

Addresshttps://api.hanzo.ai/v1/dataset/{name}
MethodDELETE
OperationriskDeleteDataset
AuthAuthorization: Bearer $HANZO_API_KEY

Disposes of one dataset and every version of it: the rows are dropped and the register is marked with what went.

This is the ONLY expiry in this plane. Neither table carries a TTL, deliberately: a table TTL is a fleet-wide clock no tenant can hold longer or shorten, which is the opposite of a retention decision belonging to the tenant whose records they are. The drop is a partition drop on (org, dataset), so the tenant is the first component of the thing being dropped and a disposal cannot be spelled across one.

The BYTES are what goes. The register keeps one disposed row per version — the name, the number, the spec, the digest and who disposed of it when — for two reasons: a retention obligation is answered by a record of the deletion, not by silence; and version numbers must stay monotone, so that after orders is disposed of and declared again the next version is 4 and not 1. A number that could be reused would make every citation of orders v3 ambiguous forever.

It is not reversible and there is no soft state in between. A version a model cited has no rows once this returns, and every read of it says so.

Request

1 field.

FieldInTypeRequiredDescription
namepathstringyesName is the dataset, from the path.

Response

StatusBodyMeaning
200riskDatasetDisposalok

200 body — 3 fields.

FieldInTypeAlwaysDescription
datasetbodystringDataset is the dataset that was disposed of.
rowsbodyintegerRows is how many rows they held between them, as the REGISTER recorded them when each was materialised — not a count of what the drop deleted, which is gone by…
versionsbodyintegerVersions is how many versions went.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Dataset API · All Hanzo APIs · Interactive reference

How is this guide?

On this page