[
https://issues.apache.org/jira/browse/PHOENIX-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Palash Chauhan updated PHOENIX-7294:
------------------------------------
Description:
In PHOENIX-6883, we validate LAST_DDL_TIMESTAMPS for PTables used in queries or
upserts. We should do this only for entities present in SYSTEM.CATALOG i.e.
PTableType is one of TABLE, VIEW, INDEX or SYSTEM.
For other PTableTypes, there is no row in SYSTEM.CATALOG and hence there is no
LAST_DDL_TIMESTAMP for them. Also, for queries like `SELECT NEXT VALUE FOR
SEQUENCE`, the PTable used by the query plan has tableType=null.
was:
In PHOENIX-6883, we validate LAST_DDL_TIMESTAMPS for PTables used in queries or
upserts. We should do this only for entities present in SYSTEM.CATALOG i.e.
PTableType is one of TABLE, VIEW, INDEX or SYSTEM.
For other PTableTypes, there is no row in SYSTEM.CATALOG and hence there is no
LAST_DDL_TIMESTAMP for them. Also, for queries like `SELECT NEXT VALUE FOR
SEQUENCE`, the PTable used by the query plan has tableType=null.
> Validate DDL timestamps only for Tables, Views and Indexes
> ----------------------------------------------------------
>
> Key: PHOENIX-7294
> URL: https://issues.apache.org/jira/browse/PHOENIX-7294
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Palash Chauhan
> Assignee: Palash Chauhan
> Priority: Major
>
> In PHOENIX-6883, we validate LAST_DDL_TIMESTAMPS for PTables used in queries
> or upserts. We should do this only for entities present in SYSTEM.CATALOG
> i.e. PTableType is one of TABLE, VIEW, INDEX or SYSTEM.
> For other PTableTypes, there is no row in SYSTEM.CATALOG and hence there is
> no LAST_DDL_TIMESTAMP for them. Also, for queries like `SELECT NEXT VALUE FOR
> SEQUENCE`, the PTable used by the query plan has tableType=null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
