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] Phase 1 of PIP-370 support disable create topics on remote cluster through replication #23169

Merged
merged 5 commits into from
Aug 23, 2024

Conversation

poorbarcode
Copy link
Contributor

@poorbarcode poorbarcode commented Aug 14, 2024

Motivation

see also PIP-370: configurable remote topic creation in geo-replication

Modifications

Next PRs

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 4.0.0 milestone Aug 14, 2024
@poorbarcode poorbarcode self-assigned this Aug 14, 2024
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Aug 14, 2024
@poorbarcode poorbarcode changed the title [draft] [improve] [broker] Phase 1 of PIP-370 support disable create topics on remote cluster through replication [improve] [broker] Phase 1 of PIP-370 support disable create topics on remote cluster through replication Aug 16, 2024
@codelipenghui
Copy link
Contributor

/pulsarbot run-failure-checks

@codecov-commenter
Copy link

codecov-commenter commented Aug 21, 2024

Codecov Report

Attention: Patch coverage is 83.78378% with 6 lines in your changes missing coverage. Please review.

Project coverage is 74.58%. Comparing base (bbc6224) to head (34a9816).
Report is 540 commits behind head on master.

Files Patch % Lines
...er/service/persistent/GeoPersistentReplicator.java 62.50% 5 Missing and 1 partial ⚠️
Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #23169      +/-   ##
============================================
+ Coverage     73.57%   74.58%   +1.01%     
- Complexity    32624    34211    +1587     
============================================
  Files          1877     1918      +41     
  Lines        139502   144657    +5155     
  Branches      15299    15813     +514     
============================================
+ Hits         102638   107898    +5260     
+ Misses        28908    28503     -405     
- Partials       7956     8256     +300     
Flag Coverage Δ
inttests 27.69% <37.83%> (+3.10%) ⬆️
systests 24.75% <10.81%> (+0.42%) ⬆️
unittests 73.93% <83.78%> (+1.09%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...org/apache/pulsar/broker/ServiceConfiguration.java 99.03% <100.00%> (-0.36%) ⬇️
.../org/apache/pulsar/broker/admin/AdminResource.java 76.26% <100.00%> (-1.37%) ⬇️
...pulsar/broker/admin/impl/PersistentTopicsBase.java 69.71% <100.00%> (+4.25%) ⬆️
...ache/pulsar/broker/service/AbstractReplicator.java 65.80% <100.00%> (-19.20%) ⬇️
...rg/apache/pulsar/client/impl/PulsarClientImpl.java 75.55% <100.00%> (+1.24%) ⬆️
...er/service/persistent/GeoPersistentReplicator.java 76.14% <62.50%> (-1.88%) ⬇️

... and 525 files with indirect coverage changes

@poorbarcode poorbarcode merged commit 44f9860 into apache:master Aug 23, 2024
51 checks passed
poorbarcode added a commit that referenced this pull request Aug 28, 2024
…n remote cluster through replication (#23169)

(cherry picked from commit 44f9860)
nikhil-ctds pushed a commit to datastax/pulsar that referenced this pull request Aug 28, 2024
…n remote cluster through replication (apache#23169)

(cherry picked from commit 44f9860)
(cherry picked from commit 9553c33)
srinath-ctds pushed a commit to datastax/pulsar that referenced this pull request Aug 28, 2024
…n remote cluster through replication (apache#23169)

(cherry picked from commit 44f9860)
(cherry picked from commit 9553c33)
grssam pushed a commit to grssam/pulsar that referenced this pull request Sep 4, 2024
@lhotari
Copy link
Member

lhotari commented Sep 11, 2024

@poorbarcode why did we cherry-picked PIP-370 changes to branch-3.0, but branch-3.3 was skipped? Asked that on the dev mailing list thread, https://lists.apache.org/thread/onvgpx4vr1184tzjl2ngxog674zgltgk .

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.

5 participants