[IGNITE-17149] Separation of the PageMemoryStorageEngineConfigurationSchema into in-memory and persistent

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-beta1
• Labels: ignite-3
• Epic Link: Pluggable Storage
• Ignite Flags: Docs Required
• Assignee: Kirill Tkalenko
• Reporter: Kirill Tkalenko
• Reviewer: Aleksandr Polovtsev
• Created: 09/Jun/22 15:13
• Updated: 13/Oct/22 12:00
• Resolved: 27/Jun/22 10:24

Description

Problem

At the moment, the org.apache.ignite.internal.storage.pagememory.configuration.schema.PageMemoryStorageEngineConfigurationSchema contains configuration for in-memory and persistent org.apache.ignite.internal.pagememory.configuration.schema.PageMemoryDataRegionConfigurationSchema, which can be inconvenient for the user for several reasons:

• PageMemoryDataRegionConfigurationSchema contains the configuration for in-memory and the persistent case, which can be confusing because it's not obvious which properties to set for each;
• User does not have the ability to set a different size PageMemoryStorageEngineConfigurationSchema#pageSize for in-memory and the persistent case;
• When creating a table through SQL, it would be more convenient for the user to simply specify the engine and use the default region than specify the data region, let's look at the examples.

CREATE TABLE user (id INT PRIMARY KEY, name VARCHAR(255)) ENGINE pagememory dataRegion='in-memory' 
CREATE TABLE user (id INT PRIMARY KEY, name VARCHAR(255)) ENGINE pagememory dataRegion='persistnet'

CREATE TABLE user (id INT PRIMARY KEY, name VARCHAR(255)) ENGINE in-memory-pagememory
CREATE TABLE user (id INT PRIMARY KEY, name VARCHAR(255)) ENGINE persistnet-pagememory

Implementation proposal

Divide by two (in-memory and persistent):

• org.apache.ignite.internal.pagememory.configuration.schema.PageMemoryDataRegionConfigurationSchema
• org.apache.ignite.internal.storage.pagememory.configuration.schema.PageMemoryStorageEngineConfigurationSchema
• org.apache.ignite.internal.storage.pagememory.PageMemoryStorageEngine

Issue Links

• blocks: IGNITE-17208 Change storage engine names based on PageMemory
• blocks: IGNITE-17210 Modification of documentation on data regions for PageMemory
• Dependency: IGNITE-17197 Change the default storage engine (for tables)
• is blocked by: IGNITE-17148 Support for abstract configuration
• links to: GitHub Pull Request #892