Skip to content

Conversation

@gaborkaszab
Copy link
Collaborator

REST catalog's client-side table cache contains table suppliers that can be used to construct table objects. These suppliers encapsulate different building blocks of a table, including TableMetadata. Lazy snapshot loading populates the list of snapshots in-place within TableMetadata. As a result, loading the full list of snapshots will also update the table supplier in the table cache. After loading the full snapshot list once, all the later answers from the table cache will contains this full snapshot list.

REST catalog's client-side table cache contains table suppliers
that can be used to construct table objects. These suppliers encapsulate
different building blocks of a table, including TableMetadata.
Lazy snapshot loading populates the list of snapshots in-place within
TableMetadata. As a result, loading the full list of snapshots will
also update the table supplier in the table cache. After loading
the full snapshot list once, all the later answers from the table
cache will contains this full snapshot list.
@gaborkaszab
Copy link
Collaborator Author

Additional context: this was identified as one of the potential follow-ups for the basic freshness-aware loading functionality. When I started working on this I realized that this in fact already works, so I added a new test for coverage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant