[ 
https://issues.apache.org/jira/browse/IGNITE-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762736#comment-16762736
 ] 

Ignite TC Bot commented on IGNITE-11193:
----------------------------------------

{panel:title=--> Run :: All: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3018194&buildTypeId=IgniteTests24Java8_RunAll]

> MVCC TX: the query with specified explicit patririons fails
> -----------------------------------------------------------
>
>                 Key: IGNITE-11193
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11193
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc, sql
>    Affects Versions: 2.7
>            Reporter: Taras Ledkov
>            Assignee: Igor Seliverstov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If the explicit partitions specified by {{SqlFieldsQuery#setPartitions}} are 
> placed on the several nodes the query fails at the partition reservation 
> ({{GridDhtTxQueryEnlistFuture.checkPartitions}}) with error: "{{Cannot run 
> update query. Node must own all the necessary partitions.}}"
> *Root cause*: MVCC DML doesn't map the requests 
> {{GridNearTxQueryEnlistRequest}}. Each node received the messages with all 
> explicit partitions. 
> *Proposal fix*: use the partitions/node mapping similar to SELECT queries. 
> See more:
> - {{GridH2QueryRequest#partitions}}
> - {{ReducePartitionsSpecializer#ReducePartitionsSpecializer}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to