[
https://issues.apache.org/jira/browse/IGNITE-27078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Blinov updated IGNITE-27078:
---------------------------------------
Description:
We need to utilize API described in
https://issues.apache.org/jira/browse/IGNITE-26995.
BuildIndexCommandHandler#handleInternally should exit the closure if storage
engine needs it.
was:
We need to utilize API described in
https://issues.apache.org/jira/browse/IGNITE-26995.
MV GC worker should exit the closure if storage engine needs it. There's
already such a mechanism for a failed {{{}tryLock{}}}, so implementing it
should not be difficult.
> Use "stop" hint in BuildIndexCommandHandler#handleInternally
> ------------------------------------------------------------
>
> Key: IGNITE-27078
> URL: https://issues.apache.org/jira/browse/IGNITE-27078
> Project: Ignite
> Issue Type: Improvement
> Components: storage engines ai3
> Reporter: Viacheslav Blinov
> Assignee: Viacheslav Blinov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> We need to utilize API described in
> https://issues.apache.org/jira/browse/IGNITE-26995.
> BuildIndexCommandHandler#handleInternally should exit the closure if storage
> engine needs it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
