You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/05/29 11:01:00 UTC

[jira] [Updated] (IGNITE-17765) Sql. Introduce cache for parsed statements

     [ https://issues.apache.org/jira/browse/IGNITE-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Orlov updated IGNITE-17765:
--------------------------------------
    Labels: ignite-3 sql-performance tech-debt  (was: ignite-3 tech-debt)

> Sql. Introduce cache for parsed statements
> ------------------------------------------
>
>                 Key: IGNITE-17765
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17765
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3, sql-performance, tech-debt
>
> 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. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)