You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "gaborkaszab (via GitHub)" <gi...@apache.org> on 2026/01/22 11:58:42 UTC
[I] Potential follow-up steps for freshness-aware table loading in REST catalog [iceberg]
gaborkaszab opened a new issue, #15109:
URL: https://github.com/apache/iceberg/issues/15109
### Feature Request / Improvement
- Update docs with new configs for table cache.
There is no page currently for REST catalog configs, probably create a dedicated one under [Catalog properties](https://iceberg.apache.org/docs/latest/configuration/#catalog-properties).
- Freshness-aware lazy snapshot loading
Metadata tables could benefit from this when catalog is in `REFS` mode. `TableMetadata.snapshotSupplier` should go through and update `RESTSessionCatalog.tableCache`
- Freshness-aware loading in `RESTTableOperations`
refresh() and commit() could also do freshness-aware loading and update the table cache. However, the implementation might not be trivial. One potential way to do this is to pass a callback to the ops from `RESTSessionCatalog` that's to be run after loadTable or updateTable communication and can keep the table cache up to date.
Note, for updateTable there are no creds and configs so that part couldn't be updated.
Note, in order to update creds and configs in refresh(), we have to update FileIO that is final atm.
- Expose table cache metrics for observability
We can have an on-demand API that returns `cacheMetricsReport`. Also we can consider sending such through the catalog's metrics reporter (maybe this is too much after each loadTable)
- Credential lifetime check
Before we update the table cache we can check if the credential lifetime was provided in the LoadTableResponse. If yes, and the expiration is "close" (could be configurable) then we can decide not to add the table to cache.
### Query engine
None
### Willingness to contribute
- [x] I can contribute this improvement/feature independently
- [ ] I would be willing to contribute this improvement/feature with guidance from the Iceberg community
- [ ] I cannot contribute this improvement/feature at this time
--
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-unsubscribe@iceberg.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Potential follow-up steps for freshness-aware table loading in REST catalog [iceberg]
Posted by "yadavay-amzn (via GitHub)" <gi...@apache.org>.
yadavay-amzn commented on issue #15109:
URL: https://github.com/apache/iceberg/issues/15109#issuecomment-4423301796
Hi @gaborkaszab — I'd be interested in picking up one of the follow-up items listed here. Which one would be most useful to tackle first? I'm thinking either the docs update for REST catalog cache configs or the freshness-aware loading in `RESTTableOperations`, but happy to go wherever the need is greatest.
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Potential follow-up steps for freshness-aware table loading in REST catalog [iceberg]
Posted by "gaborkaszab (via GitHub)" <gi...@apache.org>.
gaborkaszab commented on issue #15109:
URL: https://github.com/apache/iceberg/issues/15109#issuecomment-4429517897
Hi @yadavay-amzn ,
I've covered the doc part recently. The freshness-aware loading in the ops could be useful. I found it overly complicated myself to implement compared to the gain, but feel free to give it a try.
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Potential follow-up steps for freshness-aware table loading in REST catalog [iceberg]
Posted by "gaborkaszab (via GitHub)" <gi...@apache.org>.
gaborkaszab commented on issue #15109:
URL: https://github.com/apache/iceberg/issues/15109#issuecomment-3784028556
cc @danielcweeks @nastra @pvary
Any inputs are appreciated! Let me know which ones from the list make sense!
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org