[IGNITE-19305] Index alive after drop indexed column

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0
• Component/s: sql
• Labels: ignite-3
• Assignee: Pavel Pereslegin
• Reporter: Alexander Belyak
• Created: 18/Apr/23 14:39
• Updated: 04/Sep/24 16:10
• Resolved: 08/May/23 14:33

Description

In documentation I see: "If the column was indexed, the index has to be dropped manually in advance by using the 'DROP INDEX' command." But it seems like an alpha version limitation.

Unable to create index with the same name after dropping indexed column:

create table tindex(
id int primary key,
v1 int, 
v2 int);
create index titest on tindex(v1, v2)
alter table tindex drop column v1;
create index titest on tindex(v2);

error:

[Code: 0, SQL State: 50000]  Exception while executing query [query=create index titest on tindex(v2)]. Error message:IGN-SQL-17 TraceId:5f61df67-cc61-4eb1-98be-3bbaa25a7c44 IGN-SQL-17 TraceId:5f61df67-cc61-4eb1-98be-3bbaa25a7c44 Index already exists [name="PUBLIC"."TITEST"]

Expected behaviour:

1) index titest drop while dropping v1 columnd

2) index titest successfully created on the last DDL operation.

Issue Links

• is related to: IGNITE-19456 Dropping one column of the composite index makes impossible queries to other columns in the index
• links to: GitHub PR #2018
• links to: GitHub Pull Request #2018