[jira] [Commented] (IGNITE-18600) Meta Storage Watch events must be atomically persisted in the Vault

["Alexander Lapin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679840#comment-17679840 ] 

Alexander Lapin commented on IGNITE-18600:
------------------------------------------

[~apolovtcev] LGTM, thx. Merged to main.

> Meta Storage Watch events must be atomically persisted in the Vault
> -------------------------------------------------------------------
>
>                 Key: IGNITE-18600
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18600
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Before IGNITE-18397 all data, that has been processed by Meta Storage Watches, was automatically persisted in the Vault. In IGNITE-18397 this feature was removed, which breaks the expected design. This feature should be re-implemented with the following guarantees:
> # Only keys that match any of the registered watches should be saved to the Vault;
> # Data should be saved to the Vault atomically in a single batch along with the applied revision;
> # If any of the Watch Listeners throws an exception, then no data should be saved.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)