[jira] [Commented] (PHOENIX-2885) Refresh client side cache before throwing not found exception

["James Taylor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372805#comment-15372805 ] 

James Taylor commented on PHOENIX-2885:
---------------------------------------

We could get fancy to handle detection of dropped entities (columns, views, sequences, etc.) through some kind of zk trickery, but not sure if it's worth it - we can file a separate JIRA for that. Often destructive deletions are disallowed in production systems anyway.

> 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)