[
https://issues.apache.org/jira/browse/IGNITE-15617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15617:
---------------------------------
Description:
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
was:
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.
It should be considered to separate public and internal API.
> TableManager API improvement
> -----------------------------
>
> Key: IGNITE-15617
> URL: https://issues.apache.org/jira/browse/IGNITE-15617
> Project: Ignite
> Issue Type: Improvement
> 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)
