[ https://issues.apache.org/jira/browse/IGNITE-16395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-16395: --------------------------------------- Labels: calcite2-required calcite3-required (was: ) > Calcite engine. Implement correct copy-on-write on schema objects change > ------------------------------------------------------------------------ > > Key: IGNITE-16395 > URL: https://issues.apache.org/jira/browse/IGNITE-16395 > Project: Ignite > Issue Type: Improvement > Reporter: Aleksey Plekhanov > Priority: Major > Labels: calcite2-required, calcite3-required > > Currently, we only copy the schemas list when any schema object changes (see > {{{}SchemaHolderImpl.rebuild(){}}}), but it can lead to some problems. For > example, during planning, if some index dropped concurrently there will be > NPE after {{tbl.getIndex(String)}} in some rules. So, we should copy the > table containing this index and copy the schema containing this table at > least for DROP INDEX command. -- This message was sent by Atlassian Jira (v8.20.1#820001)