[
https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375698#comment-15375698
]
James Taylor commented on PHOENIX-2885:
---------------------------------------
Add {{AND COLUMN_FAMILY IS NULL}} and then I think it's fine. We'll need to
handle the add column cases across all clients when we support custom fields.
Also, one other case is detecting when an index has been added. We'd handle
that case already for transactional tables, but for non transactional tables &
views, indexes wouldn't be seen until the table/view expires from the cache
(not the end of the world, though).
> 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)
