[jira] [Updated] (IGNITE-20680) Postpone destroying table data while table is reachable for RO transactions via Catalog

["Andrey Mashenkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Mashenkov updated IGNITE-20680:
--------------------------------------
    Summary: Postpone destroying table data while table is reachable for RO transactions via Catalog  (was: Move table to RO state when executing DROP TABLE)

> Postpone destroying table data while table is reachable for RO transactions via Catalog
> ---------------------------------------------------------------------------------------
>
>                 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)