Skip to content

[ADLA - ADLS] - Adding pageable extension for Catalog ACL APIs and removing childrenNum property#2353

Merged
anuchandy merged 5 commits intoAzure:masterfrom
ro-joowan:catalog-pageable-store-bugfix-childproperty
Jan 30, 2018
Merged

[ADLA - ADLS] - Adding pageable extension for Catalog ACL APIs and removing childrenNum property#2353
anuchandy merged 5 commits intoAzure:masterfrom
ro-joowan:catalog-pageable-store-bugfix-childproperty

Conversation

@ro-joowan
Copy link
Copy Markdown
Contributor

@ro-joowan ro-joowan commented Jan 29, 2018

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

* 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
@AutorestCI
Copy link
Copy Markdown

Did a commit to Azure/azure-sdk-for-python:
Azure/azure-sdk-for-python@be62c19

@AutorestCI
Copy link
Copy Markdown

Did a commit to Azure/azure-sdk-for-go:
Azure/azure-sdk-for-go@b5e3dc0

@AutorestCI
Copy link
Copy Markdown

This commit was treated and no generation was made for Azure/azure-sdk-for-python

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/datalake-analytics/data-plane/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

File: specification/datalake-store/data-plane/readme.md
Before the PR: Warning(s): 0 Error(s): 6
After the PR: Warning(s): 0 Error(s): 6

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@AutorestCI
Copy link
Copy Markdown

This commit was treated and no generation was made for Azure/azure-sdk-for-go

@anuchandy
Copy link
Copy Markdown
Member

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": {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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."
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why we are removing the default from responses section?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

@anuchandy
Copy link
Copy Markdown
Member

We are removing childrenNum property but bit confused why we are removing this? Is it the case that service doesn't support this and always return null?

@ro-joowan
Copy link
Copy Markdown
Contributor Author

@anuchandy Yes, the service doesn't support that property and it is always null.

@ro-joowan
Copy link
Copy Markdown
Contributor Author

@anuchandy I have addressed the example errors in my latest commit. Thank you

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/datalake-analytics/data-plane/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

File: specification/datalake-store/data-plane/readme.md
Before the PR: Warning(s): 0 Error(s): 6
After the PR: Warning(s): 0 Error(s): 6

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@AutorestCI
Copy link
Copy Markdown

This commit was treated and no generation was made for Azure/azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

This commit was treated and no generation was made for Azure/azure-sdk-for-go

@anuchandy
Copy link
Copy Markdown
Member

anuchandy commented Jan 30, 2018

@ro-joowan thanks for the response and fixing the model errors.

Summary:

  1. Removed the property childrenNum because presence of this property was bug in swagger. Service never return such a property so client always see null for this. Related SOF issue

  2. Changed AclList to pageable.

  3. Removed bunch of default entries from the response section of Catalog ACL operations in order to consistent with other operation groups. These default has not model defined hence they were only used for doc purposes.

@anuchandy anuchandy merged commit d3af35e into Azure:master Jan 30, 2018
@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-ruby

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants