riskMaterializeDatasetWithHttpInfo method

Future<Response> riskMaterializeDatasetWithHttpInfo(
  1. String name
)

Materialise the declared version into immutable rows

Builds the declared version into immutable rows and answers 202 as soon as the attempt is on record. It never holds the request open for the work: a materialisation is a bounded warehouse scan, and letting an HTTP client's timeout be a data plane's timeout is how one tenant's retry loop becomes everyone's outage. ONE materialisation runs per org at a time; a second is refused rather than queued, because a queue admits the same work later and the honest answer to "again" while one is running is that one is running. Only a DECLARED version is admitted. A published version is immutable, and a version whose earlier attempt did not complete is never re-attempted — that would union two runs' rows under one number and make the digest a lie. In both cases the answer is to declare a new version, which is what a second run over a moving source honestly is.

Note: This method returns the HTTP Response.

Parameters:

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

Implementation

Future<Response> riskMaterializeDatasetWithHttpInfo(String name,) async {
  // ignore: prefer_const_declarations
  final path = r'/v1/dataset/{name}/materialize'
    .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,
    'POST',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}