You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2023/04/04 16:33:00 UTC
[jira] [Updated] (IGNITE-16985) Design table management flow (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Chudov updated IGNITE-16985:
----------------------------------
Attachment: (was: VersionedValuesUpdates.yuml)
> Design table management flow (part 1)
> -------------------------------------
>
> Key: IGNITE-16985
> URL: https://issues.apache.org/jira/browse/IGNITE-16985
> Project: Ignite
> Issue Type: Task
> Reporter: Alexander Lapin
> Assignee: Denis Chudov
> Priority: Major
> Labels: ignite-3
> Attachments: onTableCreate.svg, onTableCreate.yuml, onTableDrop.svg, onTableDrop.yuml, table.svg, table.yuml
>
>
> As a part of the issue planed:
> # Draw a time diagram of all operations: createTable(), dropTable(), table(), tables().
> # Emphases of correctness work of causality tokens: tablesByIdVv.
> # Reflect cross components interactions. Components: Schema manager, SQL manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now).
>
> The task for this ticket is to make a detailed diagram of the current flow, to ease the design itself.
> Definition of done:
> We have detailed and clear description of table manager flows and the ticket IGNITE-18989 is enriched with details about the flaws we want to fix.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)