[
https://issues.apache.org/jira/browse/IGNITE-28295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-28295:
---------------------------------------
Description:
Currently, full table schema diffs calculations are bound to table version
numbers: that is, if table version number did not change, we consider that the
schema has not changed and there is no diff. But in IGNITE-22990, we'll need to
consider changes in index statuses for the needs of schema change compatibility
validation, so we need to make the approach more flexible.
The idea is that:
# We add more conditions when deciding whether there is a 'diff' or not
# We use catalog versions instead of table versions as components of cache keys
> Support schema-sync related changes not bound to table version
> --------------------------------------------------------------
>
> Key: IGNITE-28295
> URL: https://issues.apache.org/jira/browse/IGNITE-28295
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> Currently, full table schema diffs calculations are bound to table version
> numbers: that is, if table version number did not change, we consider that
> the schema has not changed and there is no diff. But in IGNITE-22990, we'll
> need to consider changes in index statuses for the needs of schema change
> compatibility validation, so we need to make the approach more flexible.
> The idea is that:
> # We add more conditions when deciding whether there is a 'diff' or not
> # We use catalog versions instead of table versions as components of cache
> keys
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
