[IGNITE-20106] Check that client schema version matches server-side schema version

• 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
• Created: 01/Aug/23 07:06
• Updated: 04/Sep/24 16:10
• Resolved: 23/Oct/23 14:36

Description

As per https://cwiki.apache.org/confluence/display/IGNITE/IEP-110%3A+Schema+synchronization%3A+basic+schema+changes#IEP110:Schemasynchronization:basicschemachanges-Overallflow , the schema version that the client sends with each request should be validated against the server-side schema version corresponding to the given table in the tx. If it does not match, SCHEMA_VERSION_MISMATCH_ERR should be sent to the client along with the correct server-side schema version.

The check should be done on a tx coordinator. Also, the coordinator must check that all the tuples sent by the client (in the same request) are encoded using the same schema version.

The IEP defines baseTs as tableEnlistTs(tx, table). On the first iteration, we should implement a simpler way to calculate baseTs (max(beginTs, tableCreationTs) to allow created tables to 'appear' in a transaction or even simply beginTs). The full-blown baseTs calculation will be implemented in IGNITE-20108. It makes sense to do it later because it requires substantially more work to only support a not-to-common use-case (ALTER TABLEs after a transaction started, but before it enlisted the table).

Issue Links

• is fixed by: IGNITE-19397 Thin 3.0: Return an error to client when outdated schema is used
• is fixed by: IGNITE-19837 Java thin 3.0: Retry outdated schema error
• is related to: IGNITE-20416 IncompatibleSchemaException thrown when schema change is compatible
• is related to: IGNITE-20415 Internal IncompatibleSchemaException is thrown from public API