phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
Date Tue, 02 May 2017 18:21:04 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-2885:
----------------------------------
    Description: 
We have the ability currently to tell Phoenix how stale we're will to have the metadata through
our UPDATE_CACHE_FREQUENCY feature[1]. By default, when a table is created, unless explicitly
specified, there is no UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration
parameter to specify a default value when a CREATE TABLE statement is executed. In addition,
when a VIEW is created, we should inherit the UPDATE_CACHE_FREQUENCY value from the parent
(unless it's explicitly specified) and then fallback to the new default config value.

[1] https://phoenix.apache.org/language/index.html#options

  was: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.


> Set default value for UPDATE_CACHE_FREQUENCY
> --------------------------------------------
>
>                 Key: PHOENIX-2885
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2885
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Maddineni Sukumar
>             Fix For: 4.11.0
>
>
> We have the ability currently to tell Phoenix how stale we're will to have the metadata
through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when a table is created, unless
explicitly specified, there is no UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix
configuration parameter to specify a default value when a CREATE TABLE statement is executed.
In addition, when a VIEW is created, we should inherit the UPDATE_CACHE_FREQUENCY value from
the parent (unless it's explicitly specified) and then fallback to the new default config
value.
> [1] https://phoenix.apache.org/language/index.html#options



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message