You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2022/07/25 14:06:00 UTC
[jira] [Updated] (IGNITE-17411) Prepared statements support for Ignite 3
[ https://issues.apache.org/jira/browse/IGNITE-17411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yury Gerzhedovich updated IGNITE-17411:
---------------------------------------
Labels: ignite-3 (was: )
> Prepared statements support for Ignite 3
> ----------------------------------------
>
> Key: IGNITE-17411
> URL: https://issues.apache.org/jira/browse/IGNITE-17411
> Project: Ignite
> Issue Type: Epic
> Components: sql
> Reporter: Yury Gerzhedovich
> Priority: Major
> Labels: ignite-3
>
> Ignite 3 should support prepared statements for SQL. It should bring performance increase for particular cases when user have one query with different parameters. We could get rid of query string parsing for every execution (despite of caching, due to cache could be invalidated and not effective), get rid of exchange of query fragments between a nodes, and any other optimization.
> Prepared statements should be supported as for server and for client, both sides.
>
> This epic contains tasks related to the goal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)