You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2023/03/28 18:25:00 UTC
[jira] [Assigned] (IGNITE-19113) Refactoring after implementing index building
[ https://issues.apache.org/jira/browse/IGNITE-19113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko reassigned IGNITE-19113:
----------------------------------------
Assignee: Kirill Tkalenko
> Refactoring after implementing index building
> ---------------------------------------------
>
> Key: IGNITE-19113
> URL: https://issues.apache.org/jira/browse/IGNITE-19113
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> So that the implementation of building indexes is not too large, then this ticket will have refactoring:
> * Reduce code duplication in *org.apache.ignite.internal.storage.index.HashIndexStorage* and *org.apache.ignite.internal.storage.index.SortedIndexStorage* implementations based on RocksDB, PageMemory, and test;
> * Consider moving the omission of write commands to a common place when they are processed in *org.apache.ignite.internal.table.distributed.raft.PartitionListener#onWrite*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)