apache / apache/pulsar-client-cpp
[Bug] MaxMessageSize might be incorrect when accessing multiple clusters
- Dominant language
- C++
- Stars
- 71
- Forks
- 90
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 3
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar-client-cpp/issues) and found nothing similar.
### Version
3.5.0
### Minimal reproduce step
See https://github.com/apache/pulsar/pull/22306
### What did you expect to see?
...
### What did you see instead?
...
### Anything else?
_No response_
### Are you willing to submit a PR?
- [x] I'm willing to submit a PR!
Contributor guide
Research direction
Start by reviewing the linked Apache Pulsar pull request and the C++ client behavior in version 3.5.0. Reproduce access to multiple clusters and compare the reported MaxMessageSize with the expected limit; done means the size is correct and verified across the affected cluster configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100