You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/05/29 13:25:00 UTC

[jira] [Created] (IGNITE-19587) Sql. Remove execution-related part from IgniteTable

Konstantin Orlov created IGNITE-19587:
-----------------------------------------

             Summary: Sql. Remove execution-related part from IgniteTable 
                 Key: IGNITE-19587
                 URL: https://issues.apache.org/jira/browse/IGNITE-19587
             Project: Ignite
          Issue Type: Improvement
          Components: sql
            Reporter: Konstantin Orlov


Currently, {{org.apache.ignite.internal.sql.engine.schema.IgniteTable}} interface provides access to the internal table to access the data. This was convinient because event produced by {{TableManager}} contains both table object and its descriptor.

With upcoming {{CatalogService}} this won't be the case, because catalog manages objects' descriptors only. 

We need to rework {{LogicalRelImplementor}} in a way to acquire table object from a manager rather than from IgniteTable. This makes migration to {{CatalogService}} possible.
h4. Implementation Note
 * It would be nice to leave {{LogicalRelImplementor}} synchronous, awaiting objects' futures outside
 * Method {{org.apache.ignite.internal.sql.engine.schema.IgniteTable#table}} should be removed, as well as {{UpdateableTable}} from extends list of {{org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)