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

ASF subversion and git services commented on GEODE-7273:
--------------------------------------------------------

Commit 0015532d553cf436002fc090e3f83f9a3ac12b07 in geode's branch 
refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0015532 ]

GEODE-7273: Able to detect not colocated transaction (#4170)

* GEODE-7273: Able to detect not colocated transaction

  * Able to detect not colocated transaction if it is caused by the first 
operation on a
    replicate region and then on a partitioned region.
  * Make sure transaction host can detect this and throw 
TransactionDataNotColocatedException.
  * Transaction host will throw appropriate TransactionException based on the 
operations
    exectued.
  * Remote non host will rely on the TransactionException thrown from the tx 
host.


> Geode transaction should throw TransactionDataNotColocatedException if the 
> transaction is on replicate region then partitioned region
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7273
>                 URL: https://issues.apache.org/jira/browse/GEODE-7273
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: GeodeCommons
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> A client transaction should fail with TransactionDataNotColocatedException 
> instead of TransactionDataRebalancedException if transaction worked on the 
> replicate regions first and then worked on an entry in a partitioned region 
> where primary bucket is on another node.
> User should not work on replicate region first in a transaction, but Geode 
> should throw correct exception as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to