From 6110696ebe5801aec3f3f888d30dabbd590012e9 Mon Sep 17 00:00:00 2001 From: Serdar Ozmen Date: Tue, 26 Dec 2023 10:31:22 +0300 Subject: [PATCH] Adding the transactions deprecation notice to all 5.x series. (#942) --- .../pages/creating-a-transaction-interface.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/modules/transactions/pages/creating-a-transaction-interface.adoc b/docs/modules/transactions/pages/creating-a-transaction-interface.adoc index 369833456..69ed4bba9 100644 --- a/docs/modules/transactions/pages/creating-a-transaction-interface.adoc +++ b/docs/modules/transactions/pages/creating-a-transaction-interface.adoc @@ -1,5 +1,11 @@ = Creating a Transaction Interface +[CAUTION] +.Deprecation Notice for Transactions +==== +Hazelcast will deprecate transactions in the 5.4 release. An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs. +==== + You create a `TransactionContext` object to begin, commit and rollback a transaction. You can obtain transaction-aware instances of queues, maps, sets, lists and multimaps via `TransactionContext`, work with