Hi all, While working with the REST Catalog, I noticed that there doesn't appear to be a client-side table metadata cache implementation similar to what is available for the Flink and Spark catalogs, where a catalog instance can be wrapped in a CachingCatalog through configuration.
I am wondering if there has been any discussion about providing a client-side caching layer for the REST Catalog as well, perhaps for environments where the REST server itself doesn't implement caching or when further reducing calls to the catalog from the client is desirable. Would it make sense to have a similar CachingCatalog wrapper for the REST Catalog to provide a consistent caching mechanism across different catalog types? If this is a desirable feature and not already being worked on, I would be happy to contribute to its implementation. Thanks, Anatolii.
