[
https://issues.apache.org/jira/browse/IGNITE-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-14734:
-------------------------------------
Description:
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()
will throw CompactionException on corresponding initial calls.
was:At present {{SimpleInMemoryKeyValueStorage}} already has compaction
functionality but it is question: who and when should invoke {{compact}} method.
> 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: Andrey N. Gura
> Priority: Major
> Labels: iep-61, ignite-3
>
> 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() will throw CompactionException on corresponding initial calls.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
