phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maddineni Sukumar (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
Date Thu, 11 May 2017 19:35:04 GMT


Maddineni Sukumar commented on PHOENIX-2885:

1. I will look into parameterizing some tests with default update_cache_frequency param. 

2. Regarding priority as of now it is something like below.
     long updateCacheFrequency =  defaultValue!=null?defaultValue:0
        updateCacheFrequency = tableProps.updateCacheFrequency
    else if (parentTable!=null)
        updateCacheFrequency = parentTable.updateCacheFrequency

   So first priority is to current table specific property if exists, if not then we consider
parent table property, if parent table does not exists then only we consider global default
configured value. If global default value does not exists then it is zero which is default

So it is same as [~jamestaylor] mentioned above, so I am not changing anything there. 

> Set default value for UPDATE_CACHE_FREQUENCY
> --------------------------------------------
>                 Key: PHOENIX-2885
>                 URL:
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Maddineni Sukumar
>             Fix For: 4.11.0
>         Attachments: PHOENIX-2885.4.10-HBase-0.98.patch, PHOENIX-2885.v2.patch
> 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
> [1]

This message was sent by Atlassian JIRA

View raw message