You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/05/17 07:32:00 UTC
[jira] [Updated] (IGNITE-15723) Implement a component factory

     [ https://issues.apache.org/jira/browse/IGNITE-15723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evgeny Stanilovsky updated IGNITE-15723:
----------------------------------------
    Description: 
Today we have many component (managers) that configure during start node.
All of it created into the Ignite node constructor (IgniteImpl#IgniteImpl) and cannot be configurable: for example, no way to replace (or reconfigure) a Metastore for test.

There is a recommendation to create the component factory, that can to create other managers itself. It should work as now by default, but in a test we will be able to rewrite some method for test purpose.
In the ticket, need to create a default component factory and a method for IgniteManager which allow passing it. This new method does not need in ordinal cases, that means an internal interface for IgniteManager is required (IgniteManagerImpl).

  was:
Today we have many component (managers) that configure during start node.
All of it created into the Ignite node constructor (IgniteImpl#IgniteImpl) and cannot be configurable: for example, no way to replace (or reconfigure) a Metarore for test.

There is a recommendation to create the component factory, that can to create other managers itself. It should work as now by default, but in a test we will be able to rewrite some method for test purpose.
In the ticket, need to create a default component factory and a method for IgniteManager which allow passing it. This new method does not need in ordinal cases, that means an internal interface for IgniteManager is required (IgniteManagerImpl).


> Implement a component factory
> -----------------------------
>
>                 Key: IGNITE-15723
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15723
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> Today we have many component (managers) that configure during start node.
> All of it created into the Ignite node constructor (IgniteImpl#IgniteImpl) and cannot be configurable: for example, no way to replace (or reconfigure) a Metastore for test.
> There is a recommendation to create the component factory, that can to create other managers itself. It should work as now by default, but in a test we will be able to rewrite some method for test purpose.
> In the ticket, need to create a default component factory and a method for IgniteManager which allow passing it. This new method does not need in ordinal cases, that means an internal interface for IgniteManager is required (IgniteManagerImpl).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)