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

Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/03/23 10:13:00 UTC

[jira] [Assigned] (IGNITE-16266) Add unique id for indexes

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

Evgeny Stanilovsky reassigned IGNITE-16266:
-------------------------------------------

    Assignee: Evgeny Stanilovsky  (was: Andrey Mashenkov)

> Add unique id for indexes
> -------------------------
>
>                 Key: IGNITE-16266
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16266
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>              Labels: ignite-3, sql
>             Fix For: 3.0.0-alpha5
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As of now we address to index by name even internally. It could lead read another version of index which was dropped and created with another set of column . Let's introduce unique id (as we already have for tables) which could be accessed only internally and use as identifier of indexes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)