[Event Hubs] Ensure receiver is functional #3356
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ShivangiReja
added
Client
ramya-rao-a
suggested changes
May 31, 2019
| this._context.receivers[bReceiver.name] = bReceiver; | ||
| this._throwIfReceiverOrConnectionClosed(); | ||
| this._batchingReceiver = BatchingReceiver.create(this._context, this.partitionId, this._receiverOptions); | ||
| this._context.receivers[this._batchingReceiver.name] = this._batchingReceiver; |
There was a problem hiding this comment.
Looks like BatchingReceiver.create() function takes care of setting the receiver in the _context.receivers map. So we don't need this step
There was a problem hiding this comment.
I didn't remove this before because I was planning to do the cleanup in the separate receiver link related issue.
ramya-rao-a
approved these changes
May 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per the API proposal in #2718 (comment), we will now have a createReceiver() method on the Event Hub Client that returns a receiver.
This PR ensures that:
receive,receiveBatch,getEventIteratormethod works as expected.