Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Thu, 11 May 2017 19:35:04 +0000 (UTC)
From: "Maddineni Sukumar (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.12966415.1462830758000.190776.1494531304072@Atlassian.JIRA>
In-Reply-To: <JIRA.12966415.1462830758000@Atlassian.JIRA>
References: <JIRA.12966415.1462830758000@Atlassian.JIRA> <JIRA.12966415.1462830758314@jira-lw-us.apache.org>
Subject: [jira] [Commented] (PHOENIX-2885) Set default value for
 UPDATE_CACHE_FREQUENCY
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 11 May 2017 19:35:07 -0000


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

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
     if(tableProps.updateCacheFrequency!=null)
        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 behavior. 

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: 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
>
>         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 value.
> [1] https://phoenix.apache.org/language/index.html#options


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