[
https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993363#comment-15993363
]
Maddineni Sukumar commented on PHOENIX-2885:
--------------------------------------------
I am thinking below are the scenarios we need to consider(correct me if below
list is wrong).
Will check current behavior after making default to 10 sec.
1)Table modify like add/remove column
2)Table drop
3)Index add
4)Index modify? is it possible?
5)Index drop
Above for both Local index and secondary index
6)View create
7)View modify? is it possible
8)View drop
Thanks
> Set default value for UPDATE_CACHE_FREQUENCY
> --------------------------------------------
>
> Key: PHOENIX-2885
> URL: https://issues.apache.org/jira/browse/PHOENIX-2885
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Maddineni Sukumar
> 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)
