[PHOENIX-3823] Force cache update on MetaDataEntityNotFoundException

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.10.0
• Fix Version/s: 4.11.0
• Assignee: Maddineni Sukumar
• Reporter: James R. Taylor
• Created: 02/May/17 17:44
• Updated: 07/Jun/17 00:48
• Resolved: 02/Jun/17 17:29

Description

When UPDATE_CACHE_FREQUENCY is used, clients will cache metadata for a period of time which may cause the schema being used to become stale. If another client adds a column or a new table or view, other clients won't see it. As a result, the client will get a MetaDataEntityNotFoundException. Instead of bubbling this up, we should retry after forcing a cache update on the tables involved in the query.

The above works well for references to entities that don't yet exist. However, we cannot detect when some entities are referred to which no longer exists until the cache expires. An exception is if a physical table is dropped which would be detected immediately, however we would allow queries and updates to columns which have been dropped until the cache entry expires (which seems like a reasonable tradeoff IMHO. In addition, we won't start using indexes on tables until the cache expires.

Issue Links

• incorporates: PHOENIX-3209 Ensure scans run at specific server timestamp for UPSERT SELECT to same table