123123213weqw commented on PR #10608:
URL: https://github.com/apache/rocketmq/pull/10608#issuecomment-5030187590
@itxaiohanglover good catch — added the negative case you asked for in
c2c4e866e.
`testNamespaceV2IsolatesResourcesAcrossNamespaces` builds two clients
(InstanceA / InstanceB) and asserts:
1. Each client pins its own namespace prefix:
`configA.withNamespace("resource") == "InstanceA%resource"`, `configB` →
`InstanceB%resource`.
2. The two resolutions don't collide (positive guard).
3. **Negative isolation case**:
`configA.withoutNamespace("InstanceB%resource")` does NOT reduce to the bare
`resource` — it stays prefixed with the foreign namespace, so configA can't
"claim" it. This is the exact symptom reported in #9341: before the fix,
namespaceV2 was ignored, both clients resolved to the same un-prefixed
resource, and consumers in one namespace could see the other.
Local CI is in `action_required` (first-time-contributor approval), so the
test hasn't been validated by the project's GitHub Actions yet — happy to share
repro steps or run them on a box if that helps.
--
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]
