riskDeleteDatasetWithHttpInfo method

Future<Response> riskDeleteDatasetWithHttpInfo(
  1. String name
)

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. 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.

Note: This method returns the HTTP Response.

Parameters:

  • String name (required): Name is the dataset, from the path.

Implementation

Future<Response> riskDeleteDatasetWithHttpInfo(String name,) async {
  // ignore: prefer_const_declarations
  final path = r'/v1/dataset/{name}'
    .replaceAll('{name}', name);

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'DELETE',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}