You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, database deletes are soft deletes. They mark the database as deleted in the Catalog and rename it so that the name can be used, but keep the underlying files around.
Databases marked for deletion should be hard deleted after some period of time. Let's set this to 72 hours. Once a database has been soft deleted, 72 hours later, a background task should remove all underlying table files and then remove the database and its schema from the Catalog.
We should also have an API and CLI to run this process earlier for a specific database. I.e. a user deletes a database. Then they can make another call to have that database hard deleted. The follow up call should use the database ID as an identifier, not the name.
The text was updated successfully, but these errors were encountered:
User must have an option available to them to do a hard delete (CLI option). This can be as a flag/option of the existing delete table command or as a new command (former preferred).
For consistency, do we want this flag for delete database too, so the user can perform the whole step in a single command?
Seems like --permanent would be an appropriate name for the flag.
Currently, database deletes are soft deletes. They mark the database as deleted in the Catalog and rename it so that the name can be used, but keep the underlying files around.
Databases marked for deletion should be hard deleted after some period of time. Let's set this to 72 hours. Once a database has been soft deleted, 72 hours later, a background task should remove all underlying table files and then remove the database and its schema from the Catalog.
We should also have an API and CLI to run this process earlier for a specific database. I.e. a user deletes a database. Then they can make another call to have that database hard deleted. The follow up call should use the database ID as an identifier, not the name.
The text was updated successfully, but these errors were encountered: