[
https://issues.apache.org/jira/browse/IGNITE-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-20990:
------------------------------------
Description:
*Motivation:*
At the moment storage profiles defined for the tables and zones accordingly,
but the storage engine layer still use the region-based configurations. We need
to switch storage engine configuration to profiles too.
{*}Definition of done:{*}{*}{*}
* The storage profiles configuration must initiate appropriate storage
profiles in the each storage engine
*Implementation notes:*
- Change the *StorageEngineConfigurationSchema to implement the
StorageEngineConfigurationSchema (it the parent of storage profiles
configuration)
- Make *DataStorageModule use the new non-root
*StorageEngineConfigurationSchema, which is the part of StoragesConfiguration
- Due to the fact, that there is no default storage profile at all, we need to
remove the default region abstraction and change all builtin configs to the
appropariate value, which support default region of table creation DDL
Note: at the moment it can be difficult to remove all stuff connected with data
regions in zones and tables, so, the separate issue for final code cleanup
created IGNITE-21385
was:
- Change the *StorageEngineConfigurationSchema to implement the
StorageEngineConfigurationSchema
- Make *DataStorageModule use the new non-root
*StorageEngineConfigurationSchema, which is the part of StoragesConfiguration
- Implement the appropariate mechanism to handle default config values if there
is no StoragesConfiguration engine entity of the needed type (aipersist, aimem
and etc.), because at the moment defaults loading from the root engine
configuration, but this approach will not work anymore.
- Due to the fact, that there is no default storage profile at all, we need to
remove the default region abstraction and change all builtin configs to the
appropariate value, which support default region of table creation DDL
> Switch to storage-profile based configs in storage engine
> ---------------------------------------------------------
>
> Key: IGNITE-20990
> URL: https://issues.apache.org/jira/browse/IGNITE-20990
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Gusakov
> Assignee: Kirill Gusakov
> Priority: Major
> Labels: ignite-3
>
> *Motivation:*
> At the moment storage profiles defined for the tables and zones accordingly,
> but the storage engine layer still use the region-based configurations. We
> need to switch storage engine configuration to profiles too.
> {*}Definition of done:{*}{*}{*}
> * The storage profiles configuration must initiate appropriate storage
> profiles in the each storage engine
> *Implementation notes:*
> - Change the *StorageEngineConfigurationSchema to implement the
> StorageEngineConfigurationSchema (it the parent of storage profiles
> configuration)
> - Make *DataStorageModule use the new non-root
> *StorageEngineConfigurationSchema, which is the part of StoragesConfiguration
> - Due to the fact, that there is no default storage profile at all, we need
> to remove the default region abstraction and change all builtin configs to
> the appropariate value, which support default region of table creation DDL
> Note: at the moment it can be difficult to remove all stuff connected with
> data regions in zones and tables, so, the separate issue for final code
> cleanup created IGNITE-21385
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
