[IGNITE-11541] Dynamic columns and indexes can be lost after the cluster restart

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.8
• Component/s: cache, persistence, sql
• Ignite Flags: Docs Required
• Assignee: Alexey Goncharuk
• Reporter: Roman Guseinov
• Created: 14/Mar/19 07:53
• Updated: 07/Oct/19 16:07
• Resolved: 25/Mar/19 15:59

Description

The case is the following:

1. Run a server node (persistence enabled. static cache configuration with queryEnities).
2. Add/drop column/index via DDL.
3. Restart the node with the same configuration.
4. The changes are lost...

It seems the issue is related to merging cache metadata.

There are some workarounds:

1. Remove/comment cache configuration. After the restart, the metadata will be loaded from the persistence store. This will work for a rolling restart.
2. Make the same changes in the configuration (update queryEntity). It requires the whole cluster restart.

Reproducer is attached.

Issue Links

• is caused by: IGNITE-11604 Drop column does not remove column from internal schema
• is duplicated by: IGNITE-9489 CorruptedTreeException on index create.
• is duplicated by: IGNITE-11520 SQL schema is overwritten by static query entity configuration
• relates to: IGNITE-11608 Document static persistent caches and DDL behavior
• links to: GitHub Pull Request #6318