FANNG1 commented on code in PR #8696:
URL: https://github.com/apache/gravitino/pull/8696#discussion_r2434442843
##########
docs/lakehouse-iceberg-catalog.md:
##########
@@ -163,6 +164,18 @@ Users can use the following properties to configure the
security of the catalog
| `authentication.kerberos.check-interval-sec` | The check interval of
Kerberos credential for Iceberg catalog.
| 60 | No
| 0.6.0-incubating |
| `authentication.kerberos.keytab-fetch-timeout-sec` | The fetch timeout of
retrieving Kerberos keytab from `authentication.kerberos.keytab-uri`.
| 60 |
No
| 0.6.0-incubating |
+#### Table metadata cache
+
+Gravitino features a pluggable cache system for updating or retrieving table
metadata caches. It validates the location of table metadata against the
catalog backend to ensure the correctness of cached data.
+
+| Configuration item | Description
| Default value | Required | Since Version |
+|---------------------------------------|---------------------------------------------|---------------|----------|---------------|
+| `table-metadata-cache-impl` | The implement of the cache.
| (none) | No | 1.1.0 |
+| `table-metadata-cache-capacity` | The capacity of table metadata
cache. | 200 | No | 1.1.0 |
+| `table-metadata-cache-expire-minutes` | The expire minutes of table metadata
cache. | 60 | No | 1.1.0 |
+
+Gravitino provides build-in
`org.apache.gravitino.iceberg.common.cache.LocalMetadataCache` to store the
cache data in local memory. And you could implement your custom cache by
implementing `org.apache.gravitino.iceberg.common.cache.MetadataCache`
interface.
Review Comment:
I don't have strong options, the Iceberg catalog user could spead up the
table metadata load if enabling the cache, WDYT?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
