[
https://issues.apache.org/jira/browse/IGNITE-17597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-17597:
---------------------------------------
Labels: calcite calcite3-required (was: calcite calcite2-required
calcite3-required)
> Calcite engine. Indexes for table can't be used after columns added or dropped
> ------------------------------------------------------------------------------
>
> Key: IGNITE-17597
> URL: https://issues.apache.org/jira/browse/IGNITE-17597
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Blocker
> Labels: calcite, calcite3-required
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We recreate tables, but not copy indexes in schema change listener
> (\{{SchemaHolderImpl#onColumnsAdded}}, \{{SchemaHolderImpl#onColumnsDropped}})
> Reproducer:
>
> {code:java}
> public void testIndexAfterColumnsChange() {
> sql("create table t(id int)");
> sql("create index t_idx on t(id)");
> for (int i = 0; i < 100; i++)
> sql("insert into t values (?)", i);
> assertQuery("select * from t where id = 0")
> .matches(QueryChecker.containsIndexScan("PUBLIC", "T", "T_IDX"))
> .check();
> sql("alter table t add column new_col int");
> assertQuery("select * from t where id = 0")
> .matches(QueryChecker.containsIndexScan("PUBLIC", "T", "T_IDX"))
> .check();
> } {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
