[IGNITE-17765] Sql. Introduce cache for parsed statements

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: sql
• Labels: ignite-3 sql-performance tech-debt
• Epic Link: AI3 Performance
• Assignee: Konstantin Orlov
• Reporter: Konstantin Orlov
• Created: 27/Sep/22 09:57
• Updated: 04/Sep/24 16:19
• Resolved: 05/Jul/23 10:26

Description

Parsing of a SQL statement is fairly expensive operation. We could reduce query processing time by introducing a cache of statement text to parsed syntax tree.

Suggested solution is as follow: when query text is passed to a query processor, it should be parsed first, then we need to check if such statement is already in a statements cache. If it is not, then statementId (type of long, locally unique) should be assigned to the statement and pair <statementId, parsed tree> should be passed next to the query optimizer. Query optimizer, in turn, check if the query with given statementId is alredy optimized.

Issue Links

• causes: IGNITE-19866 Sql. Failed to optimize DELETE query plan.
• duplicates: IGNITE-17360 Sql. Introduce cache for parsed sql AST
• duplicates: IGNITE-19556 Sql. Implement cache for parsing sql requests.
• is related to: IGNITE-19358 Sql. PrepareServiceImpl prepareDML cache does not take dynamic parameters into account
• links to: GitHub Pull Request #2164
• links to: GitHub Pull Request #2280