[IGNITE-20044] Validate schema eligibility on each read/write operation in an RW transaction

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: iep-110 ignite-3
• Epic Link: Schema synchronization
• Assignee: Roman Puchkovskiy
• Reporter: Roman Puchkovskiy
• Reviewer: Ivan Bessonov
• Created: 25/Jul/23 11:19
• Updated: 04/Sep/24 16:09
• Resolved: 13/Sep/23 06:57

Description

As per https://cwiki.apache.org/confluence/display/IGNITE/IEP-110%3A+Schema+synchronization%3A+basic+schema+changes#IEP110:Schemasynchronization:basicschemachanges-Whenschemachangesarevalidated (item 2), we must check whether a schema effective at operationTs (for each read/write operation in an RW transaction) is different from the initial schema (at the beginning of the transaction for the table). If it's different, we should throw an exception (that will cause the transaction to be aborted).

Issue Links

• causes: IGNITE-20416 IncompatibleSchemaException thrown when schema change is compatible
• causes: IGNITE-20415 Internal IncompatibleSchemaException is thrown from public API
• is blocked by: IGNITE-19770 Add a mechanism to wait till a schema is available via Schema Sync at a ts
• is duplicated by: IGNITE-20109 Abort a transaction on a read/write if the schema has already changed
• links to: GitHub Pull Request #2566