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
When an iceberg table is dropped, the metadata and data files associated with that table is deleted. However, the .crc files that are created by the Hadoop file system driver are left in place. The .crc files are also left in place any time an Iceberg table data file is deleted (for example, through a merge or partition delete). This may not be noticeable when using an HDFS filesystem, but it is obvious when using the Hadoop driver to access local files.
The problem is when a temporary table is re-used for importing data and then dropped, the directory can quickly fill up with .crc files.
Steps to reproduce (Using Trino 465)
Create an Iceberg catalog and enable the Hadoop File system:
fs.hadoop.enabled=true
Create a table, insert a row, and drop the table.
Look at the directory contents and notice that it is full of .crc files, but not the original files.
When an iceberg table is dropped, the metadata and data files associated with that table is deleted. However, the .crc files that are created by the Hadoop file system driver are left in place. The .crc files are also left in place any time an Iceberg table data file is deleted (for example, through a merge or partition delete). This may not be noticeable when using an HDFS filesystem, but it is obvious when using the Hadoop driver to access local files.
The problem is when a temporary table is re-used for importing data and then dropped, the directory can quickly fill up with .crc files.
Steps to reproduce (Using Trino 465)
The text was updated successfully, but these errors were encountered: