[
https://issues.apache.org/jira/browse/IGNITE-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy resolved IGNITE-20109.
----------------------------------------
Resolution: Duplicate
> Abort a transaction on a read/write if the schema has already changed
> ---------------------------------------------------------------------
>
> Key: IGNITE-20109
> URL: https://issues.apache.org/jira/browse/IGNITE-20109
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: iep-110, ignite-3
> Fix For: 3.0.0-beta2
>
>
> As per
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-110%3A+Schema+synchronization%3A+basic+schema+changes#IEP110:Schemasynchronization:basicschemachanges-Whenschemachangesarevalidated
> , we should check schema on each read/write operation inside an RW
> transaction (using the operationTs to obtain the 'current' schema) and fail
> the operation (and abort the transaction) if the schema is different from the
> initial one (defined by baseTs), even if the schemas are compatible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
