You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2019/03/22 09:02:00 UTC

[jira] [Updated] (IGNITE-11604) Drop column does not remove column from internal schema

     [ https://issues.apache.org/jira/browse/IGNITE-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Goncharuk updated IGNITE-11604:
--------------------------------------
    Component/s: sql

> Drop column does not remove column from internal schema
> -------------------------------------------------------
>
>                 Key: IGNITE-11604
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11604
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.8
>
>
> Discovered this during the work on IGNITE-11541 (see {{StaticCacheDdlTest.testDropColumn}}).
> After a quick debug I see the following: in {{GridQueryProcessor#onSchemaFinishDiscovery}} we call {{DynamicCacheDescriptor.schemaChangeFinish(msg)}}, which eventually calls {{QuerySchema.finish(op)}}.
> Inside that method we have the following: the {{message.columns()}} collection has the field name in upper case (in the test it's "FIELD_TO_DROP"), but the entity's fields map contains lower-case names ("field_to_drop"). As a result, we do not remove the field from the query entity, this query entity is saved to the stored cache data and field re-appears after restart.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)