You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Grimstad (JIRA)" <ji...@apache.org> on 2018/09/19 11:45:00 UTC
[jira] [Comment Edited] (IGNITE-7039) SQL: local query should pin
affected partitions
[ https://issues.apache.org/jira/browse/IGNITE-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620484#comment-16620484 ]
Sergey Grimstad edited comment on IGNITE-7039 at 9/19/18 11:44 AM:
-------------------------------------------------------------------
3. Ticket Created IGNITE-9644
1,2 - fixed
was (Author: sgrimstad):
3. Ticket Created
1,2 - fixed
> 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)