You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2021/04/08 14:44:00 UTC
[jira] [Assigned] (IGNITE-14476) Get rid of using storage
implementation explicitly in ConfigurationRoot annotation
[ https://issues.apache.org/jira/browse/IGNITE-14476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Semyon Danilov reassigned IGNITE-14476:
---------------------------------------
Assignee: Semyon Danilov
> Get rid of using storage implementation explicitly in ConfigurationRoot annotation
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-14476
> URL: https://issues.apache.org/jira/browse/IGNITE-14476
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Semyon Danilov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Today we are using generated schema classes in public API, but we don't want to provide an implementation in it.
> For example:
> {code:java}
> @ConfigurationRoot(rootName = "rest", storage = InMemoryConfigurationStorage.class)
> public class RestConfigurationSchema {
> ...
> {code}
> The mention of InMemoryConfigurationStorage should be changed to a specific constant:
> {code:java}
> @ConfigurationRoot(rootName = "rest", storage = IgniteConsts.MEMORY_CONFIGURATION_STORAGE)
> public class RestConfigurationSchema {
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)