[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006819#comment-16006819 ]
Andrew Purtell commented on PHOENIX-2885: ----------------------------------------- Please fix typo. FREQUENCY, not FERQUENCY {code} public static final int DEFAULT_UPDATE_CACHE_FERQUENCY = 0; {code} Are the test failures related? The new test case checks that the setting can be updated, but do we know if updating it will actually have the intended effect? > 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 > > > 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)