shibd opened a new pull request, #969:
URL: https://github.com/apache/pulsar-client-go/pull/969

   ### Motivation
   Pulsar 2.11.0 has been 
[released](https://github.com/apache/pulsar/releases/tag/v2.11.0). Upgrade the 
versions that unit tests depend on so that they are compatible with the latest 
versions and support new features.
   
   
   ### Modifications
   - Upgrade the pulsar version that unit tests depend on to 2.11.0.
   - The `GetTopicsOfNamespace` method filters system topics. (This is the 
break change for broker v2.11.0, which has started an [email 
discussion](https://lists.apache.org/thread/qhm0zbfw0wfd1m5vj977w002qmkr5lt9). 
Temporarily fix it on the client side first)
   - Fix incorrect HTTP requests. (Because in v2.11.0 will [validate bad 
requests](https://github.com/apache/pulsar/pull/16577))
   - Remove key_shared subscribe consumer unit test-related assert(that every 
consumer will receive the message), Because consistent hashing is [enabled by 
default in v2.11.0](https://github.com/apache/pulsar/pull/13352), in scenarios 
where the number of keys is small, all messages may be sent to the same 
consumer.
   
   ### Verifying this change
   - All tests passed.
   
   
   ### Does this pull request potentially affect one of the following parts:
   
   *If `yes` was chosen, please highlight the changes*
   
     - Dependencies (does it add or upgrade a dependency): (upgrade)
     - The public API: (no)
     - The schema: (no)
     - The default values of configurations: (no)
     - The wire protocol: (no)
   
   ### Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not documented)
     - If a feature is not applicable for documentation, explain why?
     - If a feature is not documented yet in this PR, please create a followup 
issue for adding the documentation
   


-- 
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]

Reply via email to