You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2022/04/15 15:08:00 UTC

[jira] [Updated] (IGNITE-16864) TableManager refactoring.

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

Alexander Lapin updated IGNITE-16864:
-------------------------------------
    Description: We should consider TableManager refactoring in order to provide cleaner way of communication for AffinityService, SchemaManager (that's currently part of TableManager) "CalciteSchemaManager"  and TableManager itself. Please, pay attention, that it seems reasonable to include "CalciteSchemaManager" under Table umbrella.  (was: We should consider TableManager refactoring in order to provide cleaner way of communication for AffinityService, SchemaManager (that's currently part of TableManager) "CalciteSchemaManager"  and TableManager itself.)

> TableManager refactoring.
> -------------------------
>
>                 Key: IGNITE-16864
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16864
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Priority: Major
>
> We should consider TableManager refactoring in order to provide cleaner way of communication for AffinityService, SchemaManager (that's currently part of TableManager) "CalciteSchemaManager"  and TableManager itself. Please, pay attention, that it seems reasonable to include "CalciteSchemaManager" under Table umbrella.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)