[
https://issues.apache.org/jira/browse/PHOENIX-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650958#comment-16650958
]
ASF GitHub Bot commented on PHOENIX-4891:
-----------------------------------------
Github user twdsilva commented on the issue:
https://github.com/apache/phoenix/pull/363
@ChinmaySKulkarni I don't think we will ALTER TABLE UPDATE_CACHE_FREQUENCY
during SYSTEM.CATALOG upgrade. What will currently happen if we do run this
statement during the upgrade?
The index on view behavior that you describe sounds correct to me.
> An index should inherit UPDATE_CACHE_FREQUENCY setting from parent table
> ------------------------------------------------------------------------
>
> Key: PHOENIX-4891
> URL: https://issues.apache.org/jira/browse/PHOENIX-4891
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Chinmay Kulkarni
> Priority: Minor
>
> I tried:
> # creating a table with UPDATE_CACHE_FREQUENCE > 0, then creating a local
> index on the table.
> # creating a table, then creating the local index, then altering the table
> setting UPDATE_CACHE_FREQUENCY to > 0
> In both cases the local index did not inherit the setting, verified both by
> looking at SYSTEM.CATALOG, as well by behavior.
> Update: This also happens for a global index.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
