You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2024/01/26 08:39:00 UTC
[jira] [Assigned] (IGNITE-20680) Move table to RO state when executing DROP TABLE
[ https://issues.apache.org/jira/browse/IGNITE-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Mashenkov reassigned IGNITE-20680:
-----------------------------------------
Assignee: Andrey Mashenkov
> Move table to RO state when executing DROP TABLE
> ------------------------------------------------
>
> Key: IGNITE-20680
> URL: https://issues.apache.org/jira/browse/IGNITE-20680
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, when a DROP TABLE command is executed, the table is immediately stopped and its data destroyed.
> Instead, we should drop the table in next Catalog version only, so it's only accessible for RO transactions which readTimestamp is before the drop timestamp; accordingly, partition RAFT groups should not be stopped and storages destroyed yet.
> TableManager should listen for LWM changes and destroy dropped tables, which drop timestamp is below LWM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)