[
https://issues.apache.org/jira/browse/IGNITE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691410#comment-16691410
]
Ray commented on IGNITE-10314:
------------------------------
[~vozerov] Thanks for the reply.
I think it's only reasonable to return the newest QueryEntity to user.
For example, a user adds a column to a table then he reads data using Spark
data frame API which currently relies on QueryEntity to construct data frame
schema, now user will get wrong schema.
Maybe we should return the newest QueryEntity to user and store the original
QueryEntity separately?
What do you think?
> 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.0, 2.1, 2.2, 2.3, 2.4, 2.5, 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)
