[
https://issues.apache.org/jira/browse/IGNITE-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232835#comment-17232835
]
Alexey Goncharuk commented on IGNITE-13701:
-------------------------------------------
LGTM
> SQL Indexes,Tables and Schemas views in IEP-35 changed amount, order of
> columns and content
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-13701
> URL: https://issues.apache.org/jira/browse/IGNITE-13701
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Andrey N. Gura
> Assignee: Andrey N. Gura
> Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/IGNITE-12213 broke backward
> compatibility:
> * {{CACHE_GROUP_ID}} and {{CACHE_GROUP_NAME}} columns was removed from the
> {{INDEXES}} view.
> * {{CACHE_GROUP_ID}} and {{CACHE_GROUP_NAME}} columns was removed from the
> {{TABLES}} view.
> * {{SCHEMA_NAME}} column was renamed to {{NAME}} for the {{SCHEMAS}} view.
> * {{PREDEFINED}} column was added to the {{SCHEMAS}} view.
> Default columns order was changed.
> Also content of {{SCHEMAS}} view has changed in a wrong way: now view
> contains proxy indexes (it is simply wrapper and implementation detail) and
> indexes for cache key displays as {{PK}} index (it is incorrect, because
> {{PK}} index could be only for table and this kind of indexes is
> implementation detail).
> This behavior should be replaced by previous one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
