From 7115bf290e4599c629fec79b99b78a1a06481885 Mon Sep 17 00:00:00 2001 From: Christoph Strobl Date: Wed, 21 May 2014 12:55:59 +0200 Subject: [PATCH] DATAREDIS-307 - Add missing reference documentation for managed transactions. Added explanation and code samples. Original pull request: #75. --- .../docbook/reference/redis-transactions.xml | 51 +++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/docs/src/reference/docbook/reference/redis-transactions.xml b/docs/src/reference/docbook/reference/redis-transactions.xml index 2eef5abc0..19c813102 100644 --- a/docs/src/reference/docbook/reference/redis-transactions.xml +++ b/docs/src/reference/docbook/reference/redis-transactions.xml @@ -35,4 +35,55 @@ System.out.println("Number of items added to set: " + txResults.get(0)); often included raw byte arrays. If this change breaks your application, you can set convertPipelineAndTxResults to false on your RedisConnectionFactory to disable this behavior. +
+ <interfacename>@Transactional</interfacename> Support + Transaction Support is disabled by default and has explicitly to be enabled for each RedisTemplate in use by setting setEnableTransactionSupport(true). + This will force binding the RedisConnection in use to the current Thread triggering MULTI. If the transaction finishes without errors, EXEC is called, otherwise DISCARD. + Once in MULTI, RedisConnection would queue write operations, all readonly operations, such as KEYS are piped to a fresh (non thread bound) RedisConnection. + + + + +
\ No newline at end of file