-
Notifications
You must be signed in to change notification settings - Fork 160
Open
Description
What happened
Nessie version: dev
Trino version: 476
Problem: Trino doesn't delete metadata/data for Iceberg table from S3 since this commit. And if Nessie GC works fine with metadata/data for existing tables then it doesn't work for dropped tables.
Expected result: Iceberg metadata/data should be removed from S3 bucket.
How to reproduce it
Step to reproduce (trino-cli):
- Create table.
- Insert data into the table.
- Drop table.
- Run Nessie GC.
- Iceberg metadata/data still in S3 bucket.
Nessie GC log:
ionStatus=DO_NOT_INVOKE_NEXT_IF_ANY
2025-09-10 07:38:01,777 [main] INFO o.p.g.e.local.DefaultLocalExpire - live-set#8adee889-6a46-4a13-97e7-d4993db0336f: Starting expiry.
2025-09-10 07:38:01,792 [main] INFO o.p.g.e.local.DefaultLocalExpire - live-set#8adee889-6a46-4a13-97e7-d4993db0336f: Expiry finished, took PT0.014367202S, deletion summary: DeleteSummary{deleted=0, failures=0}.
Nessie-GC sweep phase for live-content-set 8adee889-6a46-4a13-97e7-d4993db0336f finished with status EXPIRY_SUCCESS after PT0.329849S, deleted 0 files, 0 files could not be deleted.
Nessie server type (docker/uber-jar/built from source) and version
docker:dev
Client type (Ex: UI/Spark/pynessie ...) and version
Trino:476
Additional information
No response
Fanourios-Chatziathanasiou, TaskDead and nicchristeller
Metadata
Metadata
Assignees
Labels
No labels