[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-2885: ---------------------------------- Summary: Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions (was: Set default value for UPDATE_CACHE_FREQUENCY) > Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions > ---------------------------------------------------------------------------- > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > Fix For: 4.11.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity > (table/column/column family, etc) is not found, we can force an update of the > client-side cache and retry the statement once. This works well for > references to entities that don't yet exist. However, we won't 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. Worst-case, we may allow queries and updates to columns which > have been dropped. In addition, we won't start using indexes on tables until > the cache expires. -- This message was sent by Atlassian JIRA (v6.3.15#6346)