[ADLA - ADLS] - Adding pageable extension for Catalog ACL APIs and removing childrenNum property#2353
Conversation
* Although paging is not supported for these operations, the design decision that we took was to provide support at the client side just in case we need to add it from the server side.
* This property is always null as brought up by this issue: Azure/azure-sdk-for-net#3770
|
Did a commit to Azure/azure-sdk-for-python: |
|
Did a commit to Azure/azure-sdk-for-go: |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-python |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-go |
|
Please take a look and fix the example validation errors |
| }, | ||
| "x-ms-paths": { | ||
| "/catalog/usql/databases/{databaseName}/acl?op=GRANTACE": { | ||
| "/catalog/usql/acl?op=GRANTACE": { |
There was a problem hiding this comment.
[For the record] Looking at the diff, at first glance it may appear that there are breaking changes in the following endpoints defs but not really - they appear so due to re-ordering of the operations in the swagger.
Catalog_GrantAclToDatabase
Catalog_GrantAcl
Catalog_RevokeAclFromDatabase
Catalog_GrantAcl
Catalog_RevokeAcl
Catalog_RevokeAclFromDatabase
@ro-joowan if possible, for future PRs it will be very helpful if we can ensure that PR shows only the changed sections.
There was a problem hiding this comment.
@anuchandy, Noted :) I should've put that part in a separate commit. Sorry about that!
| }, | ||
| "default": { | ||
| "description": "404 - Not found." | ||
| "description": "Successfully granted the access control list (ACL) entry to the Data Lake Analytics catalog." |
There was a problem hiding this comment.
Why we are removing the default from responses section?
There was a problem hiding this comment.
@anuchandy This was to follow the the rest of the APIs in that file. These ACL APIs were the first ones that I added to this Swagger file. But now as I look at them, I see that default is not really needed (or is redundant) because if it's not 200, we throw with the status code.
|
We are removing |
|
@anuchandy Yes, the service doesn't support that property and it is always null. |
|
@anuchandy I have addressed the example errors in my latest commit. Thank you |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-python |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-go |
|
@ro-joowan thanks for the response and fixing the model errors. Summary:
|
|
No modification for AutorestCI/azure-sdk-for-ruby |
Adding pageable extension for Catalog ACL APIs
Removing childrenNum property from FileStatusProperties as noted in this issue: Azure Data Lake Store SDK : FileStatusProperties.ChildrenNum Property always null azure-sdk-for-net#3770
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger