[jira] [Commented] (IGNITE-14734) Implement compaction functionality management for meta storage.

["Semyon Danilov (Jira)" <ji...@apache.org>]

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

Semyon Danilov commented on IGNITE-14734:
-----------------------------------------

For this ticket I decided to implement time-based compaction by creating a timestamp (watermark)->revision mapping. Watermark provider will be implemented in a separate ticket: https://issues.apache.org/jira/browse/IGNITE-19417

> Implement compaction functionality management for meta storage.
> ---------------------------------------------------------------
>
>                 Key: IGNITE-14734
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14734
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey N. Gura
>            Assignee: Semyon Danilov
>            Priority: Major
>              Labels: iep-61, ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> At present {{SimpleInMemoryKeyValueStorage}} already has compaction functionality but it is question: who and when should invoke {{compact}} method.
> h3. Upd:
>  * It's still an open question: who and when should invoke {{compact}} method.
>  * Besides that, it's required to fix storage compaction - IGNITE-16444
>  * Seems that we, might reuse inner ms cursors meta in order to prevent compaction of cursors over witch we are currently iterating.
>  * It's still however possible that revision-based get(), range(), and watch(), invoke(), etc will throw CompactionException on corresponding initial calls. 



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