You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Viacheslav Blinov (Jira)" <ji...@apache.org> on 2025/11/17 13:06:00 UTC

[jira] [Updated] (IGNITE-27079) Use "stop" hint in StorageUpdateHandler#handleUpdateAll

     [ https://issues.apache.org/jira/browse/IGNITE-27079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viacheslav Blinov updated IGNITE-27079:
---------------------------------------
    Description: 
We need to utilize API described in https://issues.apache.org/jira/browse/IGNITE-26995.

StorageUpdateHandler#handleUpdateAll 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.

BuildIndexCommandHandler#handleInternally 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 StorageUpdateHandler#handleUpdateAll
> -------------------------------------------------------
>
>                 Key: IGNITE-27079
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27079
>             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.
> StorageUpdateHandler#handleUpdateAll 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)