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] [broker] PIP-356 Support Geo-Replication starts at earliest position #22856

Merged
merged 1 commit into from
Jun 19, 2024

Conversation

poorbarcode
Copy link
Contributor

Motivation & Modifications

PIP-356 Support Geo-Replication starts at earliest position

Implement_ for the broker-level config

Documentation

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

Matching PR in forked repository

PR in forked repository: x

@poorbarcode poorbarcode added this to the 3.4.0 milestone Jun 6, 2024
@poorbarcode poorbarcode self-assigned this Jun 6, 2024
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Jun 6, 2024
Copy link
Contributor

@hanmz hanmz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good optimization, we have encountered this problem before

@poorbarcode poorbarcode merged commit 5fc0eaf into apache:master Jun 19, 2024
48 of 51 checks passed
poorbarcode added a commit that referenced this pull request Jun 28, 2024
poorbarcode added a commit that referenced this pull request Jun 28, 2024
nikhil-ctds pushed a commit to datastax/pulsar that referenced this pull request Jul 1, 2024
… position (apache#22856)

(cherry picked from commit 5fc0eaf)
(cherry picked from commit ab8dba3)
srinath-ctds pushed a commit to datastax/pulsar that referenced this pull request Jul 1, 2024
… position (apache#22856)

(cherry picked from commit 5fc0eaf)
(cherry picked from commit ab8dba3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants