Add Delete Files To Files metadata table

I am thinking current “files” table suffices to add “delete file” information.

Today, “entries” table already shows some delete file information, though in struct form. Example entries table “row” for positional delete file:

|status|snapshot_id        |sequence_number|data_file
|1     |3491280865879215816|2              |{1, file:/my_table_path/data/p=1/00129-2-47a2d786-6eaa-45c8-a7df-6bf1303553ec-00001.parquet, PARQUET, 0, {1}, 1, 1798, {2147483546 -> 186, 2147483545 -> 46}, {2147483546 -> 1, 2147483545 -> 1}, {2147483546 -> 0, 2147483545 -> 0}, {}, {2147483546 -> file:/my_table_path/data/p=1/00000-0-2043c59b-7a64-4c51-9a99-fb95f83ac076-00001.parquet, 2147483545 -> }, {2147483546 -> file:/my_table/data/p=1/00000-0-2043c59b-7a64-4c51-9a99-fb95f83ac076-00001.parquet, 2147483545 -> }, null, null, null, null}|

I think the current “files” table has an adequate schema to capture delete files metadata.

|content|   file_path|file_format|spec_id|partition|record_count|file_size_in_bytes|      column_sizes|    value_counts|null_value_counts|nan_value_counts|        lower_bounds|        upper_bounds|key_metadata|split_offsets|equality_ids|sort_order_id|

[aokolnychyi]

The current plan:

• Add DELETE_FILES
• Add ALL_DELETE_FILES
• Make FILES report both data and delete files
• Add DATA_FILES

[szehon-ho]

Makes sense to me, thanks guys. (or welcome to more opinions).

For completeness, I think we could also have ALL_FILES at some point (for user to conveniently see total reachability graph of Iceberg)