[
https://issues.apache.org/jira/browse/IGNITE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691221#comment-16691221
]
Ray edited comment on IGNITE-10314 at 11/19/18 3:54 AM:
--------------------------------------------------------
I have submitted a fix for this bug.
[~vozerov] Can you take a look and tell me if this is a correct fix please?
I'll fix the current tests and add more tests if this is the correct fix.
Also can you explain why you copy the QueryEntity in QuerySchema?
was (Author: ldz):
I have submitted a fix for this bug.
[~vozerov] Can you take a look and tell me if this is a correct fix please?
I'll fix the tests and more tests if this is the correct fix.
Also can you explain why you copy the QueryEntity in QuerySchema?
> QueryEntity is not updated when column and index added or dropped
> -----------------------------------------------------------------
>
> Key: IGNITE-10314
> URL: https://issues.apache.org/jira/browse/IGNITE-10314
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6, 2.7
> Reporter: Ray
> Assignee: Ray
> Priority: Critical
> Fix For: 2.8
>
>
> When user performs column and index modification operation in SQL(ex create
> index, drop index, add column, drop column), QueryEntity in
> CacheConfiguration for the modified cache is not updated.
>
> Analyse
> QueryEntity in QuerySchema is a local copy of the original QueryEntity, so
> the original QueryEntity is not updated when modification happens.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
