Palash Chauhan created PHOENIX-7381:
---------------------------------------
Summary: Client should not validate LAST_DDL_TIMESTAMP for a table
with non-zero UPDATE_CACHE_FREQUENCY if the client's cache entry is not old
enough
Key: PHOENIX-7381
URL: https://issues.apache.org/jira/browse/PHOENIX-7381
Project: Phoenix
Issue Type: Improvement
Reporter: Palash Chauhan
Assignee: Palash Chauhan
PHOENIX-6883 introduced a way for a client to validate its table metadata
before queries or updates using LAST_DDL_TIMESTAMP of the table. In the current
implementation, client will always perform an RPC to a random region server to
validate timestamps since we would set DEFAULT_UPDATE_CACHE_FREQUENCY to NEVER.
However, if a client operation involves a table with a positive
UPDATE_CACHE_FREQUENCY defined in its schema, we should skip the timestamp
validation if the client's cache entry for the table is not old enough. (just
like we skip getTable rpc if the cache entry is not old enough)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
