[
https://issues.apache.org/jira/browse/IGNITE-27082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Blinov updated IGNITE-27082:
---------------------------------------
Description:
We need to utilize API described in
https://issues.apache.org/jira/browse/IGNITE-26995.
AbstractPageMemoryTableStorage#destroyIndex should exit the closure if storage
engine needs it. See IGNITE-26996 as a hint on how it can be done (it's already
implemented in MV GC)
was:
We need to utilize API described in
https://issues.apache.org/jira/browse/IGNITE-26995.
StorageUpdateHandler#switchWriteIntents should exit the closure if storage
engine needs it. See IGNITE-26996 as a hint on how it can be done (it's already
implemented in MV GC)
> Use "stop" hint in AbstractPageMemoryTableStorage#destroyIndex
> --------------------------------------------------------------
>
> Key: IGNITE-27082
> URL: https://issues.apache.org/jira/browse/IGNITE-27082
> Project: Ignite
> Issue Type: Improvement
> Components: storage engines ai3
> Reporter: Viacheslav Blinov
> Assignee: Viacheslav Blinov
> Priority: Major
> Labels: ignite-3
>
> We need to utilize API described in
> https://issues.apache.org/jira/browse/IGNITE-26995.
> AbstractPageMemoryTableStorage#destroyIndex should exit the closure if
> storage engine needs it. See IGNITE-26996 as a hint on how it can be done
> (it's already implemented in MV GC)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
