[IGNITE-20167] Query execution flow refactoring for proper using catalog version.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: sql
• Labels: ignite-3
• Epic Link: Catalog Service
• Assignee: Andrey Mashenkov
• Reporter: Andrey Mashenkov
• Created: 04/Aug/23 15:44
• Updated: 04/Sep/24 16:09
• Resolved: 08/Aug/23 21:17

Description

As for now, we misuse SqlSchemaManager methods for getting a schema.
1. We should always use a version that is visible to a current transaction at query start, instead of getting the latest one.
2. When getting query message on remot, we wait for an actual schema version first, and then get the latest version one more time for fragment execution. However, we already know the required version and must use it, otherwise fragment can use schema "from the future".
3. Query plan cache key must have a version as well.
Also, there is a bug IgniteSchemaTable.unwrap method, we should be able to unwrap table descriptor.

Issue Links

• blocks: IGNITE-19497 Sql. Switch to SqlSchemaManager implementation on top of CatalogService
• links to: GitHub Pull Request #2413