[
https://issues.apache.org/jira/browse/PHOENIX-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Palash Chauhan resolved PHOENIX-6963.
-------------------------------------
Resolution: Fixed
> Check if LAST_DDL_TIMESTAMP is set for tables and indexes created before
> PHOENIX-6186
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-6963
> URL: https://issues.apache.org/jira/browse/PHOENIX-6963
> Project: Phoenix
> Issue Type: Sub-task
> Components: core
> Reporter: Rushabh Shah
> Assignee: Palash Chauhan
> Priority: Major
> Fix For: 5.2.0
>
>
> The whole design of PHOENIX-6883 is dependent on LAST_DDL_TIMESTAMP when we
> create/update table/view/index.
> LAST_DDL_TIMESTAMP was introduced in PHOENIX-6186. What happens to table/view
> that is created before PHOENIX-6186? In the upgrade path, do we update
> LAST_DDL_TIMESTAMP for tables that are already created?
> Also we added LAST_DDL_TIMESTAMP to an index in PHOENIX-6932. We will need to
> handle the upgrade path where we have to add LAST_DDL_TIMESTAMP to an
> existing index.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
