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

Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2022/08/05 09:05:00 UTC

[jira] [Updated] (IGNITE-17474) Rework configuration hierarchy

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

Konstantin Orlov updated IGNITE-17474:
--------------------------------------
    Labels: ignite-3  (was: )

> Rework configuration hierarchy
> ------------------------------
>
>                 Key: IGNITE-17474
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17474
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> Currently indices configuration is subtree of a table configuration. Such a hierarchy increases complexity of the objects validation.
> That could be improved by reworking the configuration in a way both indexes and tables belong to the same layer. This will give us tables' and indexes name uniqueness validation out of the box.



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