Delete Catalog Versions Manually

You can use the metadata service to set a minimum version for your catalog. All prior catalog versions will be deleted. Any catalog versions as recent as or more recent than your minimum version will not be deleted. Similarly, any partition metadata and data that is still used in current, non-deleted versions will not be deleted so that the non-deleted versions remain functional.

Warning

If you delete catalog versions, you permanently and irrevocably delete partition metadata as well as data associated with those versions. This would impact all versioned layers in the catalog. Any partition metadata and data that is still used in current, non-deleted versions will not be deleted so that the non-deleted versions remain functional.

To delete catalog versions manually, use the metadata service and set a minimum version. For the complete API reference on using the metadata service, see the Metadata API Reference.

  1. Obtain an authorization token. For instructions, see the Authentication and Authorization Developer's Guide.
  2. Use the API Lookup service to get the API endpoint for the metadata API of the catalog for the versions you want to delete. For instructions, see the API Lookup Developer's Guide.
  3. Set the minimum version for the catalog's metadata using this request:

    POST /catalogs/<catalogHrn>/versions/minimum HTTP/1.1
    Host: <Hostname for the metadata API from the API Lookup Service>
    Authorization: Bearer <Authorization Token>
    {
      "version": 1
    }
    
  4. The request returns 204 No Content.

  5. Once the minimum version has been set, you'll be able to verify it with another request:

    GET /catalogs/<catalogHrn>/versions/minimum HTTP/1.1
    Host: <Hostname for the metadata API from the API Lookup Service>
    Authorization: Bearer <Authorization Token>
    
  6. The request returns 200 OK with the response body:

    {
      "version": 1
    }
    

This procedure to delete catalog versions is done by setting a minimum version using the metadata service. For complete information on using the metadata service, see the Metadata API Reference.

  1. Obtain an authorization token. For instructions, see the Authentication and Authorization Developer's Guide.
  2. Use the API Lookup service to get the API endpoint for the metadata API of the catalog for the versions you want to delete. For instructions, see the API Lookup Developer's Guide.
  3. Set the minimum version for the catalog's metadata using this request:

    POST /catalogs/<catalogHrn>/versions/minimum HTTP/1.1
    Host: <Hostname for the metadata API from the API Lookup Service>
    Authorization: Bearer <Authorization Token>
    {
      "version": 1
    }
    
  4. The request returns 204 No Content without a response body.

  5. Once the minimum version has been set, you'll be able to verify it with another request:

    GET /catalogs/<catalogHrn>/versions/minimum HTTP/1.1
    Host: <Hostname for the metadata API from the API Lookup Service>
    Authorization: Bearer <Authorization Token>
    
  6. The request returns 200 OK with the response body:

    {
      "version": 1
    }
    

Note

The actual data deletion process will be executed asynchronously, so that the request is not blocked by the internal processing of data, e.g. the processing results from a users points of view will be eventual consistent. The physical metadata and data deletion may take up to 3 days and billing will continue for that period of time.

For complete information on using the metadata service, see the API Reference.

results matching ""

    No results matching ""