You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2023/10/04 07:54:00 UTC

[jira] [Commented] (IGNITE-20357) Design node config, zone and table storage relations

    [ https://issues.apache.org/jira/browse/IGNITE-20357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771746#comment-17771746 ] 

Alexey Scherbakov commented on IGNITE-20357:
--------------------------------------------

LGTM

> Design node config, zone and table storage relations
> ----------------------------------------------------
>
>                 Key: IGNITE-20357
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20357
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Gusakov
>            Assignee: Kirill Gusakov
>            Priority: Major
>              Labels: ignite-3
>         Attachments: Copy of Unify storage configurations for the table_zone_node levels.pdf
>
>
> *Motivation*
> We need to clarify the UX around the table storage, zone and node configs according to zone-based collocation.
> *Definition of done*
> User has the simple and predictable flow to:
> - Configure the node storage from the point of view: tables with which requirements for storage can use this node.
> - Describe on the zone creation, the nodes with which table storages can be a part of this zone
> - Describe on the table creation, which storage needed for this table and receive the error as soon as possible if chosen zone can't guarantee that its nodes have this storage



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