[
https://issues.apache.org/jira/browse/IGNITE-22638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-22638:
--------------------------------------
Fix Version/s: 3.0.0-beta2
> Catalog compaction. Add additional flush(trigger=false) method in
> MvPartitionStorage.
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-22638
> URL: https://issues.apache.org/jira/browse/IGNITE-22638
> Project: Ignite
> Issue Type: Improvement
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In general, before a checkpoint we temporarily store the calculated (in
> IGNITE-22641) timestamp, and after the checkpoint we publish that timestamp.
> Once published, this timestamp can be used to calculate the
> MinimalRequiredTime on the local node (this is out of current task scope,
> this task is only about safe publication).
> To publish this timestamp we need to add an additional
> {{flush(trigger=false)}} method in {{MvPartitionStorage}} that will not
> immediately trigger {{flush}}, but subscribe to the next one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
