[ https://issues.apache.org/jira/browse/IGNITE-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov resolved IGNITE-6415. ------------------------------------- Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > ALTER TABLE: investigate why descriptor is not updated from > GridQueryProcessor#onLocalOperationFinished > ------------------------------------------------------------------------------------------------------- > > Key: IGNITE-6415 > URL: https://issues.apache.org/jira/browse/IGNITE-6415 > Project: Ignite > Issue Type: Task > Components: sql > Affects Versions: 2.3 > Reporter: Vladimir Ozerov > Priority: Major > > For {{CREATE INDEX}} and {{DROP INDEX}} our DDL engine works as follows: > 1) Update H2 structures from DDL worker thread > 2) Then update type descriptor from > {{GridQueryProcessor#onLocalOperationFinished}} > For some reason {{ALTER TABLE}} handled differently, and we first update > descriptor, then update H2. See > {{GridQueryProcessor#processSchemaOperationLocal}}. > Two questions: > 1) Why descriptor is updated before H2? In this case we may endup in > inconsistent state if H2 failed for some reason > 2) Why we decided not to follow {{CREATE/DROP INDEX}} approach? -- This message was sent by Atlassian JIRA (v7.6.3#76005)