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 2021/10/11 14:49:00 UTC

[jira] [Updated] (IGNITE-15617) TableManager API improvements

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

Alexander Lapin updated IGNITE-15617:
-------------------------------------
    Issue Type: Epic  (was: Improvement)

> TableManager API improvements
> -----------------------------
>
>                 Key: IGNITE-15617
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15617
>             Project: Ignite
>          Issue Type: Epic
>            Reporter: Mirza Aliev
>            Priority: Major
>              Labels: ignite-3, tech-debt
>
> Currently, the TableManager's API is an API whose sole purpose is to show how TableManager works with raft, which was the runner of the alpha2 release.
> There is room for improvements for TableManager API according to components, that were supposed to use the API:  public ignite api, sql components (ddl), client nodes. 
> For example, It should be considered to separate public and internal API, public exceptions should be meaningful, etc



--
This message was sent by Atlassian Jira
(v8.3.4#803005)