[
https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373302#comment-15373302
]
Lars Hofhansl commented on PHOENIX-2885:
----------------------------------------
Not sure it's worth it.
In many case the query would compile correctly but then fail during execution
(for example when we drop a column). In that case we can catch the failed
execution and detect whether it was because of the missing
column/table/view/etc and in that case update the cache and try again (but only
once). In addition we probably want to keep the UPDATE_CACHE_FREQUENCY as an
additional option
(in case a client repeatedly issues an incorrect query with a missing column).
> Refresh client side cache before throwing not found exception
> -------------------------------------------------------------
>
> Key: PHOENIX-2885
> URL: https://issues.apache.org/jira/browse/PHOENIX-2885
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Fix For: 4.9.0
>
>
> With the increased usage of the UPDATE_CACHE_FREQUENCY property to reduce
> RPCs, we increase the chance that a separate client attempts to access a
> column that doesn't exist on the cached entity. Instead of throwing in this
> case, we can update the client-side cache. This works well for references to
> entities (columns, tables) that don't yet exist. For entities that *do*
> exist, we won't detect that they've been deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
