You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/27 20:39:00 UTC
[jira] [Commented] (PHOENIX-6932) Update LAST_DDL_TIMESTAMP for index table when add/drop/alter indexes.
[ https://issues.apache.org/jira/browse/PHOENIX-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717375#comment-17717375 ]
ASF GitHub Bot commented on PHOENIX-6932:
-----------------------------------------
shahrs87 commented on PR #1595:
URL: https://github.com/apache/phoenix/pull/1595#issuecomment-1526404757
Test `AlterTableIT#testSetPropertyDoesntUpdateDDLTimestamp` is failing after PHOENIX-6930. Don't know how I missed observing the test failure. We don't need that test anymore so removing it.
> Update LAST_DDL_TIMESTAMP for index table when add/drop/alter indexes.
> ----------------------------------------------------------------------
>
> Key: PHOENIX-6932
> URL: https://issues.apache.org/jira/browse/PHOENIX-6932
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Rushabh Shah
> Assignee: Rushabh Shah
> Priority: Major
>
> Currently we use LAST_DDL_TIMESTAMP only for data tables.
> Create LAST_DDL_TIMESTAMP when we create an index.
> Update LAST_DDL_TIMESTAMP when we alter index like disable, rebuild, unusable, usable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)