virajjasani opened a new pull request, #1955: URL: https://github.com/apache/phoenix/pull/1955
Jira: PHOENIX-7386 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 is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
