[
https://issues.apache.org/jira/browse/IGNITE-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-20680:
---------------------------------------
Epic Link: IGNITE-20473
> 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
> 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 move the table to a 'read-only' state where 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.
> From the point of view of the Catalog, the table should either be removed
> from it when executing a DROP TABLE command, or it should be marked as a
> 'read-only', this should be decided.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
