[
https://issues.apache.org/jira/browse/PHOENIX-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved PHOENIX-7386.
-----------------------------------
Resolution: Fixed
> Override UPDATE_CACHE_FREQUENCY if table has disabled indexes
> -------------------------------------------------------------
>
> Key: PHOENIX-7386
> URL: https://issues.apache.org/jira/browse/PHOENIX-7386
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.2.1, 5.3.0
>
>
> If table has UPDATE_CACHE_FREQUENCY set to non-default i.e. anything other
> than ALWAYS, depending on the value, PTable objects are cached until that
> duration at the client side metadata cache. One of the common cases for
> creating index is to create index in CREATE_DISABLE state.
> When any index is in DISABLE, CREATE_DISABLE or PENDING_ACTIVE state, Phoenix
> client does not include PTable of the corresponding index as part of the
> IndexMaintainer objects to server. Since indexes are expected to be either
> dropped or in building state from the above disabled states, it is crucial
> for Phoenix client to override the non-default value of
> UPDATE_CACHE_FREQUENCY on the base table. This would help avoid any data
> integrity issue because until the index state becomes BUILDING or ACTIVE, the
> client will continue to override UPDATE_CACHE_FREQUENCY to default value to
> let the UPSERT and/or SELECT queries to initiate getTable() RPC and override
> the client side metadata cache value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
