[
https://issues.apache.org/jira/browse/GEODE-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211180#comment-16211180
]
ASF subversion and git services commented on GEODE-3521:
--------------------------------------------------------
Commit 5a1108f0cd911e317b25613fb436531d57c55fe0 in geode's branch
refs/heads/develop from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5a1108f ]
GEODE-3521: Allow region set operations to bootstrap a transaction. (#891)
* GEODE-3521: Allow region set operations to bootstrap a transaction.
* Now Geode will bootstrap a transaction on a region set op even though
it is a first operation in the transaction.
* Add a SystemPropertyHelper class to held system properties to be set.
* User needs to set a system property to disable this new behavior.
* Do not allow an accessor to bootstrap a transaction.
* Add a PausedTXStateProxyImpl state to allow product to know if a
transaction is paused.
*Product now detects if only same thread can unpause a paused transaction.
* Do not bootstrap a new transaction again when transaction is paused.
* Add a test case for testing pause and unpause.
* A thread can not pause a transaction and start a new transaction - use
suspend and resume instead.
* Handle a situation that RegionEntry can be set in the KeyInfo when iterate
through keys.
> Allow region set op to bootstrap JTA and transaction
> ----------------------------------------------------
>
> Key: GEODE-3521
> URL: https://issues.apache.org/jira/browse/GEODE-3521
> Project: Geode
> Issue Type: Improvement
> Components: transactions
> Affects Versions: 1.2.0
> Reporter: Fred Krone
>
> Allow region set op to bootstrap the transaction. To allow backward
> compatibility, introduce a new GemFire property to allow the old behavior.
> AC:
> 1) set operation bootstraps transaction
> 2) provide a GemFire property (boolean) to opt out of this behavior for
> backwards compatibility
> 3) update unit tests notes accordingly
> 4) update documentation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)