-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Doc]Contradictory documentation of websocket features #8688
Comments
Thanks @hpvd, we should update the document. @jennifer88huang @Huanli-Meng Could you please help take a looks at this issue? |
@codelipenghui Sure. |
@jennifer88huang |
@hpvd Thanks for sharing this. Welcome to Pulsar community. |
@jennifer88huang Thanks a lot! |
|
@hpvd Thank you very much for your feedback. I'd like to explain the following points:
|
@jennifer88huang |
Describe the bug
at https://pulsar.apache.org/docs/en/client-libraries-websocket/ is written:
When looking at the Pulsar client feature matrix
at https://github.com/apache/pulsar/wiki/Client-Features-Matrix
the picture looks different: Websocket seems to offer by far the least number of features.
Expected behavior
Same statements of the documentation at both places.
Screenshots
![2020-11-24_21h09_54](https://user-images.githubusercontent.com/5681880/100146788-b7e4d280-2e9a-11eb-9c68-db4ce6e8a250.png)
Additional context
of course Feature Matrix is for 2.5.0, but latest version of pulsar would not have "solved" all red crosses in Matrix :-)
but for at least one red cross there is an open issue which contains a pull request: #8247
an other issue asks for feature parity #2678
which would of course makes this issue obsolete...
The text was updated successfully, but these errors were encountered: