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
{{ message }}
Repository navigation
[Nessie REST Catalog] Iceberg table not listing all snapshots #1105
When i run this script a second time, it is my understanding that the append method would create a new commit, and in turn, a new snapshot of the rpmd.performance iceberg table, and i should be able to see a list of snapshots in the latest metadata.json file. However, i only see the latest snapshot in the array, and running table.inspect.snapshots() only shows 1 snapshot_id, even though i see all the relevant .avro files.
May i know if there is some configuration i need to do to ensure that i can see all snapshots?
the sequence number is being tracked correctly but only the latest snapshot is being saved. my understanding is that all the past snapshots should be saved.
Hi @PetrasTYR , thank you for reporting this issue, and continuing the investigation on your side. The follow-up comment you posted is indeed very helpful. It looks like the latest metadata file only has a single snapshot, which makes me wonder if this is an issue with the specific implementation of the REST Catalog.
What you expect is correct. We should expect to see two snapshots, each snapshot with different snapshot-id but with the same snapshot summary since you are repeating the same operation twice.
Hello, I was asking some folks at project nessie's zulip chat and it seems like this is expected. Nessie provides catalog level versioning providing a consistent and reproducible state across the whole catalog; and to retain Nessie’s consistency and cross-branch/tag isolation guarantees, they deliberately choose to only return the state of a table or view as a single snapshot in Iceberg i.e. Nessie intentionally only returns the latest snapshot. Anything related to time-travel queries are to be done via Nessie instead of directly through Iceberg!
That's good to know! I didn't know much about Nessie, but I think this is helpful information for anyone else looking to debug this issue in the future. Thank you again for raising this issue and following up with the findings @PetrasTYR !
To retain Nessie’s consistency and cross-branch/tag isolation guarantees, we have deliberately chosen to only return the state of a table or view as a single snapshot in Iceberg.
Activity
[-]Iceberg table not keeping track of snapshots[/-][+]Iceberg table not listing all snapshots[/+]PetrasTYR commentedon Aug 28, 2024
For some additional background information:
i am using Nessie's REST APIs for iceberg tables.
package versions:
in the latest
metadata.jsonfile, this is how the snapshots section look like:the sequence number is being tracked correctly but only the latest snapshot is being saved. my understanding is that all the past snapshots should be saved.
sungwy commentedon Aug 28, 2024
Hi @PetrasTYR , thank you for reporting this issue, and continuing the investigation on your side. The follow-up comment you posted is indeed very helpful. It looks like the latest metadata file only has a single snapshot, which makes me wonder if this is an issue with the specific implementation of the REST Catalog.
What you expect is correct. We should expect to see two snapshots, each snapshot with different snapshot-id but with the same snapshot summary since you are repeating the same operation twice.
PetrasTYR commentedon Aug 28, 2024
Hi @sungwy , were you able to replicate the issue, by any chance?
PetrasTYR commentedon Aug 28, 2024
Hello, I was asking some folks at project nessie's zulip chat and it seems like this is expected. Nessie provides catalog level versioning providing a consistent and reproducible state across the whole catalog; and to retain Nessie’s consistency and cross-branch/tag isolation guarantees, they deliberately choose to only return the state of a table or view as a single snapshot in Iceberg i.e. Nessie intentionally only returns the latest snapshot. Anything related to time-travel queries are to be done via Nessie instead of directly through Iceberg!
sungwy commentedon Aug 28, 2024
That's good to know! I didn't know much about Nessie, but I think this is helpful information for anyone else looking to debug this issue in the future. Thank you again for raising this issue and following up with the findings @PetrasTYR !
PetrasTYR commentedon Aug 28, 2024
No worries! Closing this issue for now~
[-]Iceberg table not listing all snapshots[/-][+][Nessie REST Catalog] Iceberg table not listing all snapshots[/+]kevinjqliu commentedon Aug 30, 2024
Updated title for future reference
kevinjqliu commentedon Jan 13, 2025
https://projectnessie.org/guides/iceberg-rest/#time-travel-with-iceberg-rest