lcy999 opened a new issue, #52148: URL: https://github.com/apache/doris/issues/52148
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Description Currently, the refresh of metadata cache is configured through the FE (Frontend) settings, while the eviction time of metadata is configured via catalog properties. For large Doris clusters integrating diverse business systems, the requirements for metadata caching vary. For example, our EDM (Enterprise Decision Management) system demands zero latency, whereas the panoramic user profile system is less sensitive to latency. ### Solution Metadata cache expiration can be configured via external_cache_expire_time_minutes_after_access and file.meta.cache.ttl-second properties at the database, table, or catalog level. The priority order is: table configuration > database configuration > catalog configuration. ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
