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

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2023/05/17 10:33:00 UTC

[jira] [Updated] (IGNITE-19496) Sql. Implement SqlSchemaManager on top of CatalogService

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

Andrey Mashenkov updated IGNITE-19496:
--------------------------------------
    Summary: Sql. Implement SqlSchemaManager on top of CatalogService  (was: Implement SqlSchemaManager on top of CatalogService)

> Sql. Implement SqlSchemaManager on top of CatalogService
> --------------------------------------------------------
>
>                 Key: IGNITE-19496
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19496
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>
> As of now, SqlSchemaManager listens configuration events to compose a new schema, and does not support schema versioning.
> Let's implement SqlSchemaManager on top of CatalogService, which is already aware of schema versions.
> The new implementation may be just a caching adapter for CatalogService, which enriches Catalog with metadata that can be used by Calcite engine.



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