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 2023/02/14 12:12:00 UTC

[jira] [Updated] (IGNITE-18743) Prepare the first version of a design for schema synchronization

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

Vyacheslav Koptilin updated IGNITE-18743:
-----------------------------------------
    Labels: ignite-3  (was: )

> Prepare the first version of a design for schema synchronization
> ----------------------------------------------------------------
>
>                 Key: IGNITE-18743
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18743
>             Project: Ignite
>          Issue Type: Task
>          Components: persistence
>            Reporter: Sergey Chugunov
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> The first version has to give an overall view of how schema synchronization will work and how the most important cases will be addressed (like multiple versions of schemas, concurrent user ops and so on).
> Some ideas are explained (very briefly though) in [IEP-91|https://cwiki.apache.org/confluence/display/IGNITE/IEP-91:+Transaction+protocol#IEP91:Transactionprotocol-Lock-freeRWtransactions] document (see *Application to metadata management* section), we need to clarify them and cover with more details.
> As a result of the task should be a document and a set of several ready-for-development tasks to implement at least happy-cases of the problem.



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