Skip to content
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

[Event Hubs] Ensure receiver is functional #3175

Closed
ramya-rao-a opened this issue May 23, 2019 · 1 comment
Closed

[Event Hubs] Ensure receiver is functional #3175

ramya-rao-a opened this issue May 23, 2019 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Milestone

Comments

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented May 23, 2019

As per the API proposal in #2718 (comment), we will now have a createReceiver() method on the Event Hub Client that returns a receiver. A skeleton is already in place for the receiver. This issue is to ensure

Please note that this issue only ensures that the receive operations on the receiver works. We need to ensure #3176 is taken care of to call this feature of "createReceiver" actually complete

@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Event Hubs labels May 23, 2019
@ramya-rao-a ramya-rao-a added this to the Sprint 153 milestone May 23, 2019
@ramya-rao-a ramya-rao-a changed the title [Event Hubs] Implement createReceiver() with functional receiveBatch() [Event Hubs] Implement createReceiver() end to end May 23, 2019
@ramya-rao-a ramya-rao-a changed the title [Event Hubs] Implement createReceiver() end to end [Event Hubs] Ensure receiver is functional May 30, 2019
@ShivangiReja ShivangiReja self-assigned this May 30, 2019
@ramya-rao-a
Copy link
Contributor Author

Done with #3356

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

No branches or pull requests

2 participants