[
https://issues.apache.org/jira/browse/IGNITE-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618884#comment-16618884
]
Vladimir Ozerov commented on IGNITE-7039:
-----------------------------------------
[~SGrimstad], my comments:
# We should add {{IgniteCacheLocalQueryReservationsTest}} to test suite
# Unfortunately we cannot cache sql -> cacheIds that way because this is
potential leak: you will have as many mappings as there are unique queries. For
example, this will hit us if user attach parameters directly to SQL instead of
using parameters list, which is not that uncommon. Let's remove caching
altogether for now. Local queries will become slower, but this is OK - we are
fixing bug.
# Could you please confirm that partitions are reserved/released in DML as
well? If not, let's create a ticket for this.
> SQL: local query should pin affected partitions
> -----------------------------------------------
>
> Key: IGNITE-7039
> URL: https://issues.apache.org/jira/browse/IGNITE-7039
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Sergey Grimstad
> Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
> Attachments: 3194.patch
>
>
> When distributed query is executed, we pin cache partitions for particular
> topology version on map nodes [1]. However, it seems that we do no do that
> for local queries. This is a bug because partition with required data could
> be evicted from local node at any time, leading to incorrect results.
> [1]
> https://github.com/apache/ignite/blob/ignite-2.3/modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/twostep/GridMapQueryExecutor.java#L288
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
