Hi,

I would like to understand if Iceberg supports the following scenario:

   - At time t1, there's a table with a file f1.parquet
   - At time t2, f1.parquet is removed from the table. f1.parquet is also
   deleted from the filesystem
   - Querying table@t1 results in errors since f1.parquet is no longer
   available in the filesystem
   - At time t3, f1.parquet is recreated and added back to the table
   - Querying table@t1 now results in potentially incorrect results since
   f1.parquet is now present in the filesystem

Should there be a version identifier for each data-file in the manifest
file to handle such scenarios?

Thanks
Vivek

Reply via email to