You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/01/26 09:03:00 UTC

[jira] [Created] (IGNITE-16395) Calcite engine. Implement correct copy-on-write on schema objects change

Aleksey Plekhanov created IGNITE-16395:
------------------------------------------

             Summary: 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


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)