[IGNITE-20109] Abort a transaction on a read/write if the schema has already changed

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 3.0
• Labels: iep-110 ignite-3
• Epic Link: Schema synchronization
• Assignee: Unassigned
• Reporter: Roman Puchkovskiy
• Created: 01/Aug/23 07:51
• Updated: 04/Sep/24 16:11
• Resolved: 01/Aug/23 07:59

Description

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.

Issue Links

• duplicates: IGNITE-20044 Validate schema eligibility on each read/write operation in an RW transaction