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] PIP-384: ManagedLedger interface decoupling #23363

Merged
merged 3 commits into from
Oct 7, 2024

Conversation

lhotari
Copy link
Member

@lhotari lhotari commented Sep 27, 2024

Rendered PIP document PIP-384: ManagedLedger interface decoupling

Motivation

Apache Pulsar uses a component called ManagedLedger to handle persistent storage of messages.

The ManagedLedger interfaces and implementation were initially tightly coupled, making it difficult to introduce alternative implementations or improve the architecture.
This PIP documents changes that have been made in the master branch for Pulsar 4.0. Pull Requests #22891 and #23311 have already been merged.
This work happened after lazy consensus on the dev mailing list based on the discussion thread "Preparing for Pulsar 4.0: cleaning up the Managed Ledger interfaces".
There is one remaining PR #23313 at the time of writing this document.
The goal of this PIP is to document the changes in this area for later reference.

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

@lhotari lhotari added this to the 4.0.0 milestone Sep 27, 2024
@lhotari lhotari self-assigned this Sep 27, 2024
@github-actions github-actions bot added PIP doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. labels Sep 27, 2024
@merlimat merlimat merged commit 5451921 into apache:master Oct 7, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. PIP ready-to-test type/PIP
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants