You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2025/10/03 01:14:00 UTC
[jira] [Updated] (PHOENIX-6987) Tables with UPDATE_CACHE_FREQUENCY set to 0 should not be inserted into the client side metadata cache
[ https://issues.apache.org/jira/browse/PHOENIX-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated PHOENIX-6987:
----------------------------------
Fix Version/s: 5.4.0
(was: 5.3.0)
> Tables with UPDATE_CACHE_FREQUENCY set to 0 should not be inserted into the client side metadata cache
> ------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-6987
> URL: https://issues.apache.org/jira/browse/PHOENIX-6987
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Palash Chauhan
> Priority: Major
> Fix For: 5.4.0
>
>
> CQSI maintains a client-side metadata cache for tables. UPDATE_CACHE_FREQUENCY is a property which can be set on tables and used to decide when to update a table's metadata in the client-side cache. If the UPDATE_CACHE_FREQUENCY is set to 0, a tables's metadata should always be retrieved by getting the latest metadata from the server.
> Currently, tables with UPDATE_CACHE_FREQUENCY set to 0 are retrieved from the server each time they are accessed for a query or mutation. After every retrieval from the server, the old table ref in the cache is removed and the new one is inserted unnecessarily.
> [MetaDataCachingIT#testCacheShouldBeUsedOnlyForConfiguredTables() |https://github.com/apache/phoenix/blob/master/phoenix-core/src/it/java/org/apache/phoenix/query/MetaDataCachingIT.java#L170]can be used to confirm that the cache is used only for tables with non zero update cache frequency. This test is currently ignored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)