zooo-code opened a new pull request, #25158:
URL: https://github.com/apache/pulsar/pull/25158
<!--
### Contribution Checklist
- PR title format should be *[type][component] summary*. For details, see
*[Guideline - Pulsar PR Naming
Convention](https://pulsar.apache.org/contribute/develop-semantic-title/)*.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
-->
<!-- Either this PR fixes an issue, -->
Fixes #25128
<!-- Details of when a PIP is required and how the PIP process work, please
see: https://github.com/apache/pulsar/blob/master/pip/README.md -->
### Motivation
<!-- Explain here the context, and why you're making that change. What is
the problem you're trying to solve. -->
The logic for setting `policies.bundles` is different between
`getNamespacePolicies` (sync) and `getNamespacePoliciesAsync`:
- `getNamespacePolicies` (sync):
- bundles source:
`NamespaceBundleFactory.getBundles().getBundlesData()`
- fallback: `bundleData != null ? bundleData : policies.bundles`
- migrated fallback: `false` when LocalPolicies is absent
- `getNamespacePoliciesAsync`:
- bundles source: `LocalPolicies.bundles`
- fallback: none (only sets if `localPolicies.isPresent()`)
- migrated fallback: none
This inconsistency can cause different results when calling sync vs async
methods for the same namespace.
### Modifications
<!-- Describe the modifications you've done. -->
Aligned `getNamespacePoliciesAsync` with the sync method by:
- Using `NamespaceBundleFactory.getBundlesAsync()` instead of
`LocalPolicies.bundles`
- Applying the same fallback logic: `bundleData != null ? bundleData :
policies.bundles`
- Ensuring `migrated` field defaults to `false` when `LocalPolicies` is
absent
### Verifying this change
- [x] Make sure that the change passes the CI checks.
This change is already covered by existing tests, such as integration tests
that exercise namespace policies retrieval through both sync and async code
paths.
### Does this pull request potentially affect one of the following parts:
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
*If the box was checked, please highlight the changes*
- [ ] Dependencies (add or upgrade a dependency)
- [ ] The public API
- [ ] The schema
- [ ] The default values of configurations
- [ ] The threading model
- [ ] The binary protocol
- [ ] The REST endpoints
- [ ] The admin CLI options
- [ ] The metrics
- [ ] Anything that affects deployment
### Documentation
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
- [ ] `doc` <!-- Your PR contains doc changes. -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update
later -->
- [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->
### Matching PR in forked repository
PR in forked repository: https://github.com/zooo-code/pulsar <!-- ENTER URL
HERE -->
<!--
After opening this PR, the build in apache/pulsar will fail and instructions
will
be provided for opening a PR in the PR author's forked repository.
apache/pulsar pull requests should be first tested in your own fork since
the
apache/pulsar CI based on GitHub Actions has constrained resources and quota.
GitHub Actions provides separate quota for pull requests that are executed
in
a forked repository.
The tests will be run in the forked repository until all PR review comments
have
been handled, the tests pass and the PR is approved by a reviewer.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
