[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[ https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-15998: - Description: *AS IS* Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either. *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration was: *AS IS* Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either.{*}{*} *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration > Add configuration for system data region. > - > > Key: IGNITE-15998 > URL: https://issues.apache.org/jira/browse/IGNITE-15998 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Major > > *AS IS* > Currently, Ignite users can control only two *system region* parameters: > *initialSize* and *maxSize.* These properties are managed by > DataStorageConfiguration, but same time default and user-specified regions > have *org.apache.ignite.configuration.DataRegionConfiguration* for > configuring them. It is not wise to use the same class for the {*}system > region{*}, because there are some restrictions the codebase is relying on, > but keeping to `drill new holes` in *DataStorageConfiguration* for the > *system region* is not good either. > > *TO BE* > Implement configuration class for systemDataRegion similar to > {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more > restricted options, ready to be added more on-demand. > Move systemRegionProperties from > *org.apache.ignite.configuration.DataStorageConfiguration* to own class. > > API changes: > # Declare deprecated: > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemRe
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[ https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-15998: - Description: *AS IS* Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either.{*}{*} *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration was: *AS IS* Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either.{*}{{*}} *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration > Add configuration for system data region. > - > > Key: IGNITE-15998 > URL: https://issues.apache.org/jira/browse/IGNITE-15998 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Major > > *AS IS* > Currently, Ignite users can control only two *system region* parameters: > *initialSize* and *maxSize.* These properties are managed by > DataStorageConfiguration, but same time default and user-specified regions > have *org.apache.ignite.configuration.DataRegionConfiguration* for > configuring them. It is not wise to use the same class for the {*}system > region{*}, because there are some restrictions the codebase is relying on, > but keeping to `drill new holes` in *DataStorageConfiguration* for the > *system region* is not good either.{*}{*} > > *TO BE* > Implement configuration class for systemDataRegion similar to > {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more > restricted options, ready to be added more on-demand. > Move systemRegionProperties from > *org.apache.ignite.configuration.DataStorageConfiguration* to own class. > > API changes: > # Declare deprecated: > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfigurat
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[ https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-15998: - Description: *AS IS* Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either.{*}{{*}} *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration was: AS IS Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either.{*}{*} *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration > Add configuration for system data region. > - > > Key: IGNITE-15998 > URL: https://issues.apache.org/jira/browse/IGNITE-15998 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Major > > *AS IS* > Currently, Ignite users can control only two *system region* parameters: > *initialSize* and *maxSize.* These properties are managed by > DataStorageConfiguration, but same time default and user-specified regions > have *org.apache.ignite.configuration.DataRegionConfiguration* for > configuring them. It is not wise to use the same class for the {*}system > region{*}, because there are some restrictions the codebase is relying on, > but keeping to `drill new holes` in *DataStorageConfiguration* for the > *system region* is not good either.{*}{{*}} > > *TO BE* > Implement configuration class for systemDataRegion similar to > {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more > restricted options, ready to be added more on-demand. > Move systemRegionProperties from > *org.apache.ignite.configuration.DataStorageConfiguration* to own class. > > API changes: > # Declare deprecated: > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfigurat
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[ https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-15998: - Description: AS IS Currently, Ignite users can control only two *system region* parameters: *initialSize* and *maxSize.* These properties are managed by DataStorageConfiguration, but same time default and user-specified regions have *org.apache.ignite.configuration.DataRegionConfiguration* for configuring them. It is not wise to use the same class for the {*}system region{*}, because there are some restrictions the codebase is relying on, but keeping to `drill new holes` in *DataStorageConfiguration* for the *system region* is not good either.{*}{*} *TO BE* Implement configuration class for systemDataRegion similar to {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more restricted options, ready to be added more on-demand. Move systemRegionProperties from *org.apache.ignite.configuration.DataStorageConfiguration* to own class. API changes: # Declare deprecated: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize # Add new methods: ** org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) ** org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration # Add new configuration class org.apache.ignite.configuration.SystemDataRegionConfiguration > Add configuration for system data region. > - > > Key: IGNITE-15998 > URL: https://issues.apache.org/jira/browse/IGNITE-15998 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Major > > AS IS > Currently, Ignite users can control only two *system region* parameters: > *initialSize* and *maxSize.* These properties are managed by > DataStorageConfiguration, but same time default and user-specified regions > have *org.apache.ignite.configuration.DataRegionConfiguration* for > configuring them. It is not wise to use the same class for the {*}system > region{*}, because there are some restrictions the codebase is relying on, > but keeping to `drill new holes` in *DataStorageConfiguration* for the > *system region* is not good either.{*}{*} > > *TO BE* > Implement configuration class for systemDataRegion similar to > {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more > restricted options, ready to be added more on-demand. > Move systemRegionProperties from > *org.apache.ignite.configuration.DataStorageConfiguration* to own class. > > API changes: > # Declare deprecated: > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize > ** > org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize > # Add new methods: > ** > org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration) > ** > org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration > # Add new configuration class > org.apache.ignite.configuration.SystemDataRegionConfiguration -- This message was sent by Atlassian Jira (v8.20.1#820001)