You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by vi...@apache.org on 2024/05/27 08:42:08 UTC
(pulsar-site) branch revert-gh712 created (now 6ff9b3e10a3a)
This is an automated email from the ASF dual-hosted git repository.
visortelle pushed a change to branch revert-gh712
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
at 6ff9b3e10a3a Revert "[improve][doc]Add introduction of transaction isolation level in the txn-advanced-features.md (#712)"
This branch includes the following new commits:
new 6ff9b3e10a3a Revert "[improve][doc]Add introduction of transaction isolation level in the txn-advanced-features.md (#712)"
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(pulsar-site) 01/01: Revert "[improve][doc]Add introduction of transaction isolation level in the txn-advanced-features.md (#712)"
Posted by vi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
visortelle pushed a commit to branch revert-gh712
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
commit 6ff9b3e10a3a65602ab60070ca4e3c40980a62bb
Author: visortelle <vi...@gmail.com>
AuthorDate: Mon May 27 12:41:40 2024 +0400
Revert "[improve][doc]Add introduction of transaction isolation level in the txn-advanced-features.md (#712)"
This reverts commit b7ada2f9207297087b614f18dcac8b0676eb39bd.
---
docs/txn-advanced-features.md | 25 +------------------------
1 file changed, 1 insertion(+), 24 deletions(-)
diff --git a/docs/txn-advanced-features.md b/docs/txn-advanced-features.md
index f00aa6f858c7..8819fcf8fba3 100644
--- a/docs/txn-advanced-features.md
+++ b/docs/txn-advanced-features.md
@@ -37,33 +37,10 @@ If you want to enable authentication with transactions, follow the steps below.
2. [Configure authentication](security-overview/#authentication) in a Pulsar client.
-## Select transaction isolation level
-
-To enhance the flexibility of Pulsar transactions, they support two distinct isolation levels:
-- `READ_COMMITTED`(default): The consumer can only consume all transactional messages that have been committed.
-- `READ_UNCOMMITTED`: The consumer can consume all messages, even transactional messages that have been aborted.
-
-For different scenarios, they use different subscriptions and choose different isolation levels. One scenario might require transactions, while another might not. In general, not all subscriptions of the same topic require transaction guarantees. Some want low latency without the exact-once semantic guarantee (like a real-time monitoring system), and some must require the exactly-once guarantee (e.g., business processing systems).
-Users can freely choose different isolation levels according to different scenarios.
-
-Note that this is a subscription-level configuration, and all consumers under the same subscription must be configured with the same isolation level.
-
-In this example, the consumer builder uses the `READ_UNCOMMITTED` isolation level.
-
-```java
-Consumer<String> consumer = client
- .newConsumer(Schema.STRING)
- .topic("persistent://my-tenant/my-namespace/my-topic")
- .subscriptionName("my-subscription")
- .subscriptionType(SubscriptionType.Shared)
- .subscriptionIsolationLevel(SubscriptionIsolationLevel.READ_UNCOMMITTED) // Adding the isolation level configuration
- .subscribe();
-```
-
## Guarantee exactly-once semantics
If you want to guarantee exactly-once semantics with transactions, you can [enable message deduplication at the broker, namespace, or topic level](cookbooks-deduplication.md#enable-message-deduplication-at-namespace-or-topic-level).
## Related topics
-- To get up quickly, see [Pulsar transactions - Get started](txn-use.md).
+- To get up quickly, see [Pulsar transactions - Get started](txn-use.md).
\ No newline at end of file