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 2025/01/27 15:03:00 UTC

[jira] [Updated] (IGNITE-24322) Move SchemaSyncService to the upper level.

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

Andrey Mashenkov updated IGNITE-24322:
--------------------------------------
    Priority: Minor  (was: Major)

> Move SchemaSyncService to the upper level.
> ------------------------------------------
>
>                 Key: IGNITE-24322
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24322
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Mashenkov
>            Priority: Minor
>              Labels: ignite-3, tech-debt
>             Fix For: 3.1
>
>
> As for now, some CatalogService methods contract description involves SchemaSyncService. 
> The SchemaSyncService depends on ignite-schema module, which depends on ignite-catalog. That means it is impossible to put a link to SchemaSyncService to javadoc of CatalogService interface.
> Also, SchemaSyncService looks independent from both ignite-schema and catalog modules.



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