[
https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-2885:
----------------------------------
Description: Instead of by default doing an extra RPC per query, we should
have a default value for 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. (was: 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.)
> 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
> Fix For: 4.9.0
>
>
> Instead of by default doing an extra RPC per query, we should have a default
> value for 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)
