[Azure Search] Introduce last of the breaking changes for Azure search major version revision#7265
Merged
brjohnstmsft merged 6 commits intoAzure:masterfrom Aug 21, 2019
Conversation
added 5 commits
August 12, 2019 13:01
arv100kri
requested review from
Careyjmac,
brjohnstmsft,
jadrefke and
mgottein
Member
Author
|
NOTE: This is a draft PR, because the official swagger PR hasn't yet been merged. |
brjohnstmsft
suggested changes
Aug 15, 2019
brjohnstmsft
approved these changes
Aug 16, 2019
Pull in documentation changes
Member
Author
The swagger PR has been merged, and this PR is now "official" |
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
2 participants
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.
This commit introduces the breaking changes from the swagger pull request into the .NET SDK.
The breaking changes that'll go out as part of the next major version release are:
namepropertydegreeOfParallelismproperty, which can allow customers to specify how many API calls (if non-null, non-zero) can be made in parallel to their endpoint