amogh-jahagirdar commented on issue #9723: URL: https://github.com/apache/iceberg/issues/9723#issuecomment-1943095150
The short answer to your question is yes, I think this is expected behavior for the scenario you described because a replace will reset the history entries (the snapshot-log). As for definitions: 1.) Metadata log entry -> These log entries that are stored as part of table metadata indicate what are the historical metadata files, and at which point in time the table's metadata file was that particular metadata file 2.) latest_snapshot_id -> This is the snapshot ID that was the state of the table at the time the metadata file in the log entry was the metadata file for the table. Time travel for snapshot IDs is done on the basis of the history, you can check out more details on this [here](https://github.com/apache/iceberg/pull/5364#issuecomment-1227902420) . Since the replace eliminates the previous history it's not possible to determine this snapshot so null is returned. 3.) latest_schema_id -> This is the schema associated with the snpashot in 2). If the snapshot is null, this will also be null. 4.) latest_sequence_number -> This is the sequence number associated with the snapshot in 2. If the snapshot is null, this will also be null. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
