poorbarcode opened a new pull request, #21885: URL: https://github.com/apache/pulsar/pull/21885
### Motivation - Before [PIP-145](https://github.com/apache/pulsar/issues/14505), it used the Partitioned topic name to match the Regexp. For example, the partitioned topic `public/default/tp` has one partition named `public/default/tp-partition-0`. Pulsar will use `public/default/tp` to match the Regexp. - After [PIP-145](https://github.com/apache/pulsar/issues/14505), it used the partition name to match the Regexp. For example, the partitioned topic `public/default/tp` has one partition named `public/default/tp-partition-0`. Pulsar will use `public/default/tp-partition-0` to match the Regexp. It is a break change that is not expected; these changes are due to a mistake, and we should correct it. ### Issue If a consumer tries to subscribe to a topic with a precise regexp, it does not work. - create topic `persistent://public/default/tp` - create a consumer with regexp `persistent://public/default/tp` - the pattern consumer has no internal consumers. You can reproduce the issue by the test `testPreciseRegexpSubscribe`. - it can work when using `2.10.x` - it can not work when using `>=2.11.x` ### Modifications Revert the behavior as the original implementation(before PIP-145) ### 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: x -- 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]
