You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/12/19 11:31:00 UTC
[jira] [Updated] (IGNITE-21118) Make index non-writable when it's switched to READ_ONLY state
[ https://issues.apache.org/jira/browse/IGNITE-21118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy updated IGNITE-21118:
---------------------------------------
Description:
Most of the time, we determine index writability for an operation based on whether the index is in a writable state (REGISTERED, BACKFILLING, AVAILABLE, STOPPING) in the schema version corresponding to the beginTs of the transaction.
We should implement the following exception: the index is NOT more writable for any transaction if its *current* state has reached READ_ONLY.
> Make index non-writable when it's switched to READ_ONLY state
> -------------------------------------------------------------
>
> Key: IGNITE-21118
> URL: https://issues.apache.org/jira/browse/IGNITE-21118
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Most of the time, we determine index writability for an operation based on whether the index is in a writable state (REGISTERED, BACKFILLING, AVAILABLE, STOPPING) in the schema version corresponding to the beginTs of the transaction.
> We should implement the following exception: the index is NOT more writable for any transaction if its *current* state has reached READ_ONLY.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)