[Azure Maps] Async Batch API schema change#29284
[Azure Maps] Async Batch API schema change#29284chcmsft wants to merge 16 commits intoAzure:mainfrom
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Swagger Validation Report
|
| Compared specs (v0.10.9) | new version | base version |
|---|---|---|
| asyncBatchManagement.json | 2024-04-01-preview(8210c43) | 2024-04-01-preview(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 2 Warnings warning [Detail]
| Compared specs (v2.2.2) | new version | base version |
|---|---|---|
| package-preview-2024-04 | package-preview-2024-04(8210c43) | package-preview-2024-04(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
Error schema should define code and message properties as required.Location: AsyncBatchManagement/preview/2024-04-01-preview/asyncBatchManagement.json#L120 |
||
The error property in the error response schema should be required.Location: AsyncBatchManagement/preview/2024-04-01-preview/asyncBatchManagement.json#L120 |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
Error schema should define code and message properties as required.Location: AsyncBatchManagement/preview/2024-04-01-preview/asyncBatchManagement.json#L160 |
|
The error property in the error response schema should be required.Location: AsyncBatchManagement/preview/2024-04-01-preview/asyncBatchManagement.json#L160 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: AsyncBatchManagement/preview/2024-04-01-preview/asyncBatchManagement.json#L302 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
weidongxu-microsoft
left a comment
There was a problem hiding this comment.
You need to pass breaking changes review.
|
@mikekistler @JeffreyRichter We want to make our API schema consistent by adopting kind and id to status monitor API. |
|
@mikekistler |
ad33659 to
e1fbfba
Compare
a190a28 to
8acc589
Compare
98a9f86 to
d036d9c
Compare
|
@weidongxu-microsoft |
2dfc596 to
057bb0d
Compare
|
Changes:
|
1. Sort swagger 2. Add 2024-04-01-preview back
1d8a840 to
6d3a613
Compare
…utContainerUri and outputContainerUri
…are already in main branch
… to 2024-10-01-preview
…eview and 2024-06-01-preview as they are already in main
|
Hi, @chcmsft. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi, @chcmsft. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee. |
Change
API version change
We change the api version of AsyncBatchManagement/Route/Search from 2024-04-01-preview to 2024-10-01-preview because of the release plan. The target is to release the async batch APIs with api version 2024-10-01-preview. Thus, Route 2024-05-01-preview and 2024-06-01-preview don't contain the async batch route direction API anymore and need to remove the async batch route directions api from both 2024-05-01-preview and 2024-06-01-preview api version.
Major API Change
Request body of geocoding async batch, reverse geocoding async batch, route directions async batch
We change the design from processing one input blob and generate one output blob to processing multiple input blobs and transform them into multiple output blobs.
Thus, the
inputBlobUrlis replaced byinputFolderPath. theoutputStorageUrlis replaced byoutputFolderPath.original request body
new request body
AsyncBatchManagement Get Operation API response schema change
due to the requirement change from processing single blob to multiple blobs, I tweak the operation status response according to the request body change above.
original
new
Note
These APIs are not published yet. Thus, no breaking change concern.
Click here to open a PR for a Data Plane API.