You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/04/01 09:12:00 UTC
[jira] [Updated] (IGNITE-16750) Improve separation between public and internal interfaces of Table
[ https://issues.apache.org/jira/browse/IGNITE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-16750:
-----------------------------------------
Priority: Minor (was: Major)
> Improve separation between public and internal interfaces of Table
> ------------------------------------------------------------------
>
> Key: IGNITE-16750
> URL: https://issues.apache.org/jira/browse/IGNITE-16750
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Roman Puchkovskiy
> Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> Currently, there is a public part including Table and IgniteTables that can be used to get instances of Table; and a private part represented with TableImpl and IgniteTablesInternal that can be used to get instances of TableImpl.
> We probably need to decouple the internal and public interfaces so that they form different layers.
> Maybe we should use InternalTable in the internal code instead of using TableImpl?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)