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/24 05:17:00 UTC

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

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

Evgeny Stanilovsky commented on IGNITE-16266:
---------------------------------------------

[~korlov] , [~tledkov-gridgain] plz make a review [1]

[1] https://github.com/apache/ignite-3/pull/672/commits/8f43f9eb2bfb825cabf7d9b6241f7a2ba93fb233

In general i don`t like the idea to delegate validation logic into RelJsonReader side, but we can change it in future.

> 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)