Alexand Polyakov created IGNITE-13518:
-----------------------------------------
Summary: Change static cache configuration allowed or not and what
operations: add column, drop
Key: IGNITE-13518
URL: https://issues.apache.org/jira/browse/IGNITE-13518
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.8.1
Reporter: Alexand Polyakov
If a new node with a modified configuration cache is connected, the
configuration is merged and a new column is added. if the cluster is restarted
with a new cache configuration, the changes are ignored and the column is not
added
1. you need to determine whether to allow changing the static cache
configuration or not to allow it
2. the behavior should be the same (restart cluster, join node)
3. the behavior is not described in the documentation
4. How static cache configuration interacts with dynamic changes from SQL?
5. Export/import database schema
6. There are no messages in the application logs about changing the cache
configuration (or about a ban based on the result of point 1)
7. If the configuration can be changed, what should I do with the fields that
are missing in the new version of the configuration - delete column? if they
were added using SQL
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
