[
https://issues.apache.org/jira/browse/IGNITE-22039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-22039:
-
Description:
We need to throw an exception if the index is globally (in the catalog) in
readable status (AVAILABLE or STOPPING) but locally has not yet been built. See
TODO.
Upd:
I don’t quite understand the task of disaster recovery of indexes; I don’t need
this functionality from this ticket and it’s enough to get rid of
InconsistentIndexStateException for SortedIndexStorage#tolerantScan.
was:We need to throw an exception if the index is globally (in the catalog)
in readable status (AVAILABLE or STOPPING) but locally has not yet been built.
See TODO.
> Do not allow the index to be scanned in an inconsistent state
> -
>
> Key: IGNITE-22039
> URL: https://issues.apache.org/jira/browse/IGNITE-22039
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We need to throw an exception if the index is globally (in the catalog) in
> readable status (AVAILABLE or STOPPING) but locally has not yet been built.
> See TODO.
> Upd:
> I don’t quite understand the task of disaster recovery of indexes; I don’t
> need this functionality from this ticket and it’s enough to get rid of
> InconsistentIndexStateException for SortedIndexStorage#tolerantScan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
