How to allow Table deletion without requiring ownership on table?
Problem Description
In DBR 6 (and earlier), a non-admin user can delete a table that the user doesn't own, as long as the user has ownership on the table's parent database (perhaps through group ownership of that database). This was actually due to a bug in that DBR included ownership in its inheritance of privileges. That bug was fixed for DBR 7, so that a user must have ownership on a table in order to delete it (as described in the "DROP TABLE" requirements in the public Documentation).
This presents problems for customers used to the DBR 6 deletion requirements (as seen in ES-96920: Table ACLs Drop Table Permission Change- Migrating from 6.x to 7.xMOVED TO ENG BACKLOG). It also means that a non-admin user cannot delete a database if some other user has created a table within the database.
For comparison, PostgreSQL allows the owner of a schema (== database) to delete any object within it. This behavior seems like a sensible model, and the new Managed Catalog service will follow it in its data governance model.
How can DBR allow deletion of a table by a (non-admin) user who has ownership on the table's parent database (i.e., the user does not need to own the table in order to delete it)?
