Websocket API - Expose ReachedEndOfTopic in Reader/Consumer API

[sfescape]

It would be very helpful if there was an ability to test ReachedEndOfTopic. It's not clear to me when you can stop reading if you're only interested in traversing existing messages for a topic.

[jerrypeng]

@sfescape the Reader and Consumer API does have this functionality:

reader.hasReachedEndOfTopic()

[sfescape]

In looking at the Websocket API documentation, I don't see anything in the endpoint responses that give me that information. I understand it's available in the other interfaces.

[sijie]

@sfescape Currently this feature is not available in websocket. you can check this out for the feature parity between clients: https://github.com/apache/pulsar/wiki/Client-Features-Matrix

[sfescape]

Thank you, this feature seems to be "Reader hasMessageAvailable". This project doesn't seem to use JIRA, is there a place I can go look for any roadmap on websocket API features?

[sijie]

@sfescape we are using github issues for the issue management. the wiki page is for tracking the feature parity. we are currently catching up on c++ and python (we are almost caught up there). however regarding websocket, it is still in the backlog. we put that in low priority since there is no real asks before. we will try to prioritize it since now we are seeing requests.

[hpvd]

nice :-)
with having this, feature matrix shoud be updated: https://github.com/apache/pulsar/wiki/Client-Features-Matrix