[PHOENIX-6987] Tables with UPDATE_CACHE_FREQUENCY set to 0 should not be inserted into the client side metadata cache

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 5.3.0
• Assignee: Unassigned
• Reporter: Palash Chauhan
• Created: 21/Jun/23 19:12
• Updated: 16/Apr/24 05:53

Description

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() can be used to confirm that the cache is used only for tables with non zero update cache frequency. This test is currently ignored.