2025.1 API changes to support WebSockets, query tracing, node connection state - #142
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
There are a few breaking changes in here:
EventsResourceGroup.EnumerateAsync()andListAsync()now use WebSocket streamed searches;PagedEnumerateAsync()is introduced as a fallback to the earlier behavior,EventsResourceGroupnow usesIAsyncEnumerablefor searching/streaming, andSeqConnectionconstructors have been removed.I'll detail those alongside other changes for the release in the
dev→mainPR/release notes coming up soon.