You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2022/03/15 11:42:00 UTC

[jira] [Created] (IGNITE-16691) Storage Configuration refactoring and improvements

Sergey Chugunov created IGNITE-16691:
----------------------------------------

             Summary: Storage Configuration refactoring and improvements
                 Key: IGNITE-16691
                 URL: https://issues.apache.org/jira/browse/IGNITE-16691
             Project: Ignite
          Issue Type: Task
            Reporter: Sergey Chugunov


Currently Storage configuration in Ignite 3.0 reuses concepts right from Ignite 2.x like DataRegion.

However there are substantial differences between 2.x and 3.0 versions: when there is only one option of Storage in 2.x (off-heap page-based storage), 3.0 supports multiple types of storage (right now RocksDB implementing LSM trees model, refactored page-based storage in the near future).

With that in mind we need to refactor current configuration storage to the most abstract way, so Storage configuration entity would have only its Type (e.g. LSM or PAGE_MEMORY) and human-readable Name (in one-to-one relationship with Type).

Other implementation details like DataRegion should be hidden in polymorphic configuration.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)