ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sboi...@apache.org
Subject [08/20] ignite git commit: Clarified READ_COMMITTED behavior in cases when a value is updated inside of a transaction
Date Mon, 18 Jul 2016 09:37:49 GMT
Clarified READ_COMMITTED behavior in cases when a value is updated inside of a transaction


Project: http://git-wip-us.apache.org/repos/asf/ignite/repo
Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/005ce0f3
Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/005ce0f3
Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/005ce0f3

Branch: refs/heads/ignite-3483
Commit: 005ce0f3d05f529b0a1de64d7f6b59efb6612ee0
Parents: 8af3078
Author: Denis Magda <dmagda@gridgain.com>
Authored: Fri Jul 8 12:58:43 2016 +0300
Committer: Denis Magda <dmagda@gridgain.com>
Committed: Fri Jul 8 12:58:43 2016 +0300

----------------------------------------------------------------------
 .../main/java/org/apache/ignite/transactions/Transaction.java   | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/ignite/blob/005ce0f3/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java b/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java
index e2e7100..450b626 100644
--- a/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java
+++ b/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java
@@ -38,7 +38,10 @@ import org.apache.ignite.lang.IgniteUuid;
  *  will be provided for read operations. With this isolation level values are always read
  *  from cache global memory or persistent store every time a value is accessed. In other
words,
  *  if the same key is accessed more than once within the same transaction, it may have different
- *  value every time since global cache memory may be updated concurrently by other threads.
+ *  value every time since global cache memory may be updated concurrently by other threads.
However note that if an
+ *  update happens inside of a transaction then the new value belonging to a key will be
stored in the local
+ *  transactional map and all subsequent reads using the key will return this new value avoiding
requests to global
+ *  cache memory.
  * </li>
  * <li>
  *  {@link TransactionIsolation#REPEATABLE_READ} isolation level means that if a value was
read once


Mime
View raw message