Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add areaOfInterest and detectObject to CV API #4771

Merged
merged 4 commits into from
Dec 11, 2018
Merged

Conversation

mirzamo
Copy link
Contributor

@mirzamo mirzamo commented Dec 4, 2018

This PR has been approved in the private repo. As we are about to release these features to public, I'm sending this PR.
https://github.com/Azure/azure-rest-api-specs-pr/pull/607

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:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

* Replace the current swagger with an auto-generated one.
* Add example files for areaOfInterest and detectObject.
* Fix example validation errors for analyze and describe.
* A few fixes for generating java sdk
@openapi-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2978

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-ruby

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-ruby#2068

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2237

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#4429

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#3596

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-js

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-js#809

@yangyuan
Copy link
Member

yangyuan commented Dec 4, 2018

Hi @mirzamo, earlier today I had a meeting with Hui and Cha today.
We will need API Review Board to review the swaggers before we proceed.

"InvalidModel",
"CancelledRequest",
"NotSupportedVisualFeature",
"FailedToProcess",
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems to be a breaking change for your API - current SDKs will not be able to handle these new enums. Only enums with "modelAsString" set to true are allowed to add new enum values.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can you help clarify? If the service returns one of these new values in the JSON, aren't current clients screwed anyway?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jianghaolu Any comments?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes That's what I mean by saying the rest API is going to break the clients.

Copy link
Contributor

Choose a reason for hiding this comment

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

aren't current clients screwed anyway

This doesn't justify breaking the clients after breaking the APIs. If this list is supposed to grow you should mark "modelAsString" to true in this PR. This PR is bringing breaking changes anyways (unfortunately) but there will be no more in the future.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I changed it to true to prevent future breaking changes. Also in here.

@mirzamo
Copy link
Contributor Author

mirzamo commented Dec 7, 2018

@yangyuan I addressed all of your comments.
Regarding the API review board, I sent over the swagger and sdk, but the comments are either related to autorest which we don't have any control over it, or naming. We cannot make any changes to the names at this time since the SDKs are already shipped.

@yangyuan
Copy link
Member

yangyuan commented Dec 7, 2018

@mirzamo
Can you cc me the email thread? (alias yuanyang)
For existing issues (not related to this PR) we can totally skip them and fix them in next version, but need PM's awareness.

Copy link
Member

@yangyuan yangyuan left a comment

Choose a reason for hiding this comment

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

Look good from my side.
Also passes typo check.

"metadata": {
"width": 100,
"height": 100,
"format": "Jpeg"
Copy link
Member

Choose a reason for hiding this comment

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

Just an idea, wouldn't jpeg or JPEG be better?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree, but for all the of other services it's Jpeg and I think it's better to keep them consistent.

Copy link
Member

Choose a reason for hiding this comment

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

Just curious, what services you are referring to? I searched before and didn't find anyother..

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

Oh you mean other operations, I thought you mean other services

@jianghaolu jianghaolu merged commit 6d123b9 into Azure:master Dec 11, 2018
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
*  Add areaOfInterest and detectObject

* Replace the current swagger with an auto-generated one.
* Add example files for areaOfInterest and detectObject.
* Fix example validation errors for analyze and describe.
* A few fixes for generating java sdk

* Addressing commets: reorder some keys

* fix formatting

* Changing modelAsString parameter to ture to be able to add new values ComputerVisonErrors enum
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants