Support DataLakeStorage 10-31-19 version#7032
Conversation
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
|
Can one of the admins verify this patch? |
...fication/storage/data-plane/Microsoft.StorageDataLake/stable/2019-10-31/DataLakeStorage.json
Outdated
Show resolved
Hide resolved
erich-wang
left a comment
There was a problem hiding this comment.
@DadanielZ , please follow step 6 in https://github.com/Azure/adx-documentation-pr/wiki/Review-Process:-Adding-new-API-version:
Please note that it is time-consuming to review the file line by line for every api-version. When you are creating the swagger specification for the new api-version, please copy the swagger specification from the previous version into the new api-versioned folder and commit it. After that overwrite it with the changes for the new api-version. This makes it easy for us to review the changes.
299a476 to
6d4ed71
Compare
|
@erich-wang updated. |
| "info": { | ||
| "description": "Azure Data Lake Storage provides storage for Hadoop and other big data workloads.", | ||
| "title": "Azure Data Lake Storage REST API", | ||
| "version": "2018-11-09", |
|
@yungezz , could you assign someone to take a look at Breaking change error in CI? |
|
hi @michaeljqzq could you pls help to look at the breaking change failure? thanks. |
|
Hi @erich-wang , after investigation @michaeljqzq identified error in breakingChange tool is a tool issue, he will fix it. Pls ping me to force merge the PR when reviewing done. Thanks! |
|
@erich-wang @yungezz could you help to merge it if the review is done? |
|
@DadanielZ , we're waiting for review from azure api board, that's why I added label WaitingForAzureAPIBoard. I'll ping them if no response next week. |
|
Hi @erich-wang, could you help to ping azure api board to review? thanks! |
Already sent email this morning. |
|
@erich-wang thanks, is there anyone reviewing this PR? |
I've sent email to api review team and you were in the email thread. |
| "x-ms-parameter-location": "client" | ||
| }, | ||
| "dnsSuffix": { | ||
| "default": "dfs.core.windows.net", |
There was a problem hiding this comment.
Default values for required parameters are not allowed.
There was a problem hiding this comment.
Hi @johanste, thanks for the review. but these are not part of this PR.
I was following step 6 in https://github.com/Azure/adx-documentation-pr/wiki/Review-Process:-Adding-new-API-version:
copy the swagger specification from the previous version into the new api-versioned folder and commit it. After that overwrite it with the changes for the new api-version.
So this makes it easy for you to review the changes.
All the changes for the new API is in 6d4ed71
and c350081,
Thanks.
| "type": "boolean" | ||
| }, | ||
| "lastModified": { | ||
| "type": "string" |
There was a problem hiding this comment.
Isn't this a date-time? Or is the precision too high/more than milliseconds - and if so, is there really a need to use sub-millisecond granularity?
| } | ||
| } | ||
| }, | ||
| "Path": { |
There was a problem hiding this comment.
Are none of the properties required?
| "group": { | ||
| "type": "string" | ||
| }, | ||
| "permissions": { |
There was a problem hiding this comment.
The plural in the property name usually implies that the value is a collection (list etc.).
| "in": "header", | ||
| "required": false, | ||
| "type": "string" | ||
|
|
There was a problem hiding this comment.
While technically correct, this description is probably not the best for human consumption. I would recommend describing what the different positions mean.
If you want to provide a regex, you can do so using the pattern, minLength and maxLength properties.
|
Only one optional query parameter added. No need for full REST API review in front of board. Signed off. |
|
/azp run public.rest-api-specs |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thank you for your help! @johanste @erich-wang @NullMDR @yungezz |
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.