You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/02/09 08:19:00 UTC
[jira] [Updated] (IGNITE-11223) SQL: Make two-step plan immutable
[ https://issues.apache.org/jira/browse/IGNITE-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-11223:
-------------------------------------
Description: It should not mutate between calls. This way we will remove necessity to re-put plans to plan cache on every request. (was: Both methods are essentially two pieces of the same process - collect cache IDs for the given query, check MVCC mode. But because they are separated, we have unnecessary collection copies, "isEmpty" checks and iterations.
Provided that these methods are on a hot path, let's merge them accurately.)
> SQL: Make two-step plan immutable
> ---------------------------------
>
> Key: IGNITE-11223
> URL: https://issues.apache.org/jira/browse/IGNITE-11223
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It should not mutate between calls. This way we will remove necessity to re-put plans to plan cache on every request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)