UNREGISTER API
A data catalog API that removes a table's registration entry from a catalog without deleting the underlying data files or metadata files. This makes catalog-unbinding operations safe and reversible, and serves as a key mechanism for achieving data portability.
Timeline (last 90 days)
The UNREGISTER API removes a table's registration from the catalog but does not delete the underlying data files and metadata files.
When a table is unregistered using UNREGISTER and then re-registered in a new catalog, the data remains in object storage throughout the entire process, with no data migration occurring.
The combination of the REGISTER and UNREGISTER APIs implements the design philosophy of the catalog as a pluggable component, making the catalog a management layer that can be switched at any time.
UNREGISTER only removes the catalog-layer reference; without a data lifecycle management strategy, data files that are unregistered but retained may cause storage costs to accumulate.
All Facts (4)
The UNREGISTER API removes a table's registration from the catalog but does not delete the underlying data files and metadata files.
50%UnverifiedWhen a table is unregistered using UNREGISTER and then re-registered in a new catalog, the data remains in object storage throughout the entire process, with no data migration occurring.
50%UnverifiedThe combination of the REGISTER and UNREGISTER APIs implements the design philosophy of the catalog as a pluggable component, making the catalog a management layer that can be switched at any time.
50%UnverifiedUNREGISTER only removes the catalog-layer reference; without a data lifecycle management strategy, data files that are unregistered but retained may cause storage costs to accumulate.
50%