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.
Here's my analysis QueryEntity in QuerySchema is a local copy of the original QueryEntity, so the original QueryEntity is not updated when modification happens. I have created a ticket for this issue https://issues.apache.org/jira/browse/IGNITE-10314 But as Vlad said in the comments "public configuration is immutable, it represents initial cache parameters. So it is expected that configuration will not be updated after DDL commands. Real changes are accumulated in separate query entity which is hidden from user and used internally" But 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, so user will get wrong schema. What do you guys think? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
