After running LakeFormation UpdateTableObjects with DeleteObject, why does Athena and Glue still have the items?

Question

I am trying to delete entries from my Lake Formation Governed Table. I ran the commands via the SDK, and it all looked successful, but the linked Athena still sees the data that was supposedly deleted. Deleting the S3 resources after (since DeleteObject from the governed table doesn't adjust S3) now throws errors in Athena because the expected files are missing.

Is there something wrong with my process of deleting from Lake Formation Governed tables?

Answer

TL;DR -
You can view permissions on the databases link for databases and tables https://docs.amazonaws.cn/en_us/lake-formation/latest/dg/viewing-permissions.html

You will need drop permissions on the tables and database to remove the underlying schema from the Glue data catalog.

A Longer Read on Lake Formation Permissions -
In the Lake Formation developer guide you'll see Lake Formation and S3 have 'data' permissions. Glue and Athena via the Glue Data Catalog are referred to as 'metadata' in the context of permissions. https://docs.aws.amazon.com/pdfs/lake-formation/latest/dg/lake-formation-dg.pdf

After running LakeFormation UpdateTableObjects with DeleteObject, why does Athena and Glue still have the items?

Relevanter Inhalt