Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[improve][doc]Add introduction of transaction isolation level in the txn-advanced-features.md #712

Merged
merged 15 commits into from
Feb 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs/txn-advanced-features.md
  • Loading branch information
visortelle authored Feb 29, 2024
commit 7e0f50942a9759c49df7fb38b9703d76578b1502
2 changes: 1 addition & 1 deletion docs/txn-advanced-features.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ If you want to enable authentication with transactions, follow the steps below.
## Select transaction isolation level

To enhance the flexibility of Pulsar transactions, they support two distinct isolation levels:
- READ_COMMITTED, Consumer can only consume all transactional messages which have been committed.
- `READ_COMMITTED`(default): The consumer can only consume all transactional messages that have been committed.
- READ_UNCOMMITTED, Consumer can consume all messages, even transactional messages which have been aborted.
visortelle marked this conversation as resolved.
Show resolved Hide resolved

For different scenarios, they use different subscriptions and choose different isolation levels. One needs transaction, one does not. In general, multiple subscriptions of the same topic do not all
Expand Down
Loading