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

create New TA API version v3.1-preview.5 #13851

Merged
merged 20 commits into from
May 14, 2021

Conversation

laramume
Copy link
Contributor

@laramume laramume commented Apr 8, 2021

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Please ensure to add changelog with this PR by answering the following questions.

  1. What's the purpose of the update?
    • new API version
  2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. - April 3rd week 2021
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No, no need to refresh for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

  • Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

    • Adding new API(s)
    • Adding a new API version
    • Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
    • Adding a new service
  • Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

API CHanges from previous version

  1. Async now supports Sentiment and Opinion Mining
  2. Introduced a new query param "LoggingOptOut" to give the user to permission to not log any of their data even for 2 days(which we are currently doing)

@laramume laramume requested a review from yangyuan as a code owner April 8, 2021 17:46
@openapi-workflow-bot
Copy link

Hi, @laramume Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Apr 8, 2021

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️⚠️LintDiff: 1 Warnings warning [Detail]
    The following errors/warnings are introduced by current PR:
    Rule Message
    ⚠️ R3017 - GuidUsage Guid used in model definition 'JobMetadata' for property 'jobId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
    Location: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L2129
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️❌ModelValidation: 1 Errors, 0 Warnings failed [Detail]
    Rule Message
    ENUM_CASE_MISMATCH Enum does not match case for: Positive
    Url: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L1890
    JsonUrl: preview/v3.1-preview.5/examples/SuccessfulHealthStatusRequest.json
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️❌Cross-Version Breaking Changes: 34 Errors, 17 Warnings failed [Detail]
    The following breaking changes are detected by comparison with the latest stable version:

    Only 10 items are listed, please refer to log for more details.

    Rule Message
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L361:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L368:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L490:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L497:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L547:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L554:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L604:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L611:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L670:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L677:11


    The following breaking changes are detected by comparison with latest preview version:

    Only 10 items are listed, please refer to log for more details.

    Rule Message
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L924:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L889:13
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L903:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L872:13
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L2287:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L2170:13
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L277:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L334:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L391:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L457:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L622:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L2676:5
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L2559:5
    1027 - DefaultValueChanged The new version has a different default value than the previous one.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L924:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L889:13
    ️🔄CredScan inProgress [Detail]
    ️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation

    The following errors/warnings are introduced by current PR:

    |:speech_balloon: AutorestCore/Exception|"readme":"cognitiveservices/data-plane/TextAnalytics/readme.md",
    "tag":"release_3_1_preview.5",
    "details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
    |:speech_balloon: AutorestCore/Exception|"readme":"cognitiveservices/data-plane/TextAnalytics/readme.md",
    "tag":"release_3_1_preview.5",
    "details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
    |:speech_balloon: AutorestCore/Exception|"readme":"cognitiveservices/data-plane/TextAnalytics/readme.md",
    "tag":"release_3_1_preview.5",
    "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|

    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️🔄[Staging] Lint(RPaaS) inProgress [Detail]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Apr 8, 2021

    Swagger Generation Artifacts

    ️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️[Staging] SDK Breaking Change Tracking succeeded [Detail] [Expand]

    Breaking Changes Tracking

    ️❌ azure-sdk-for-python failed [Detail]
    • Failed [Logs]Release - Generate from 5e1ad2f. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
      cmderr	[automation_init.sh] azure-mgmt-core 1.2.2 requires azure-core<2.0.0,>=1.9.0, but you have azure-core 1.6.0 which is incompatible.
      cmderr	[automation_init.sh] ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
      cmderr	[automation_init.sh] azure-mgmt-core 1.2.2 requires azure-core<2.0.0,>=1.9.0, but you have azure-core 1.6.0 which is incompatible.
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmdout	[automation_generate.sh] [Autorest]/home/vsts/work/1/s/azure-sdk-for-python_tmp/venv-sdk/auto_temp.json does not exist!!!Error happened during codegen
      error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-python]: sh scripts/automation_generate.sh
      warn	Skip package processing as generation is failed
    ️⚠️ azure-sdk-for-java warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 5e1ad2f. SDK Automation 14.0.0
      command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
      command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
      cmderr	[generate.py] 2021-05-14 17:11:05 ERROR [Skip] readme path does not format as specification/*/resource-manager/readme.md
      warn	No file changes detected after generation
      warn	No package detected after generation
    ️❌ azure-sdk-for-go failed [Detail]
    • Failed [Logs]Release - Generate from 5e1ad2f. SDK Automation 14.0.0
      command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      command	go run ./tools/generator/main.go ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
      Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
      HttpError: Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
          at /home/vsts/work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/@octokit/request@5.4.15/node_modules/@octokit/request/dist-node/index.js:68:23
          at processTicksAndRejections (internal/process/task_queues.js:93:5)
          at async workflowPkgUpdatePR (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:330:21)
          at async Object.exports.workflowPkgMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:41:5)
          at async workflowHandleReadmeMd (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:172:9)
          at async Object.exports.workflowMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:83:9)
          at async Object.exports.sdkAutoMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/entrypoint.js:152:13)
          at async /home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/cli/cli.js:20:18
    • ️✔️cognitiveservices/v2.1/textanalytics [View full logs
      info	[Changelog] No exported changes
      error	Fatal error: Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
      error	The following packages are still pending:
      error		cognitiveservices/v2.1/textanalytics
      error		cognitiveservices/v2.0/textanalytics
    • ️✔️cognitiveservices/v2.0/textanalytics
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 5e1ad2f. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	autorest --version=V2 --typescript --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.typescript@4.4.4 --typescript-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-js/azure-sdk-for-js ../../azure-rest-api-specs/specification/cognitiveservices/data-plane/TextAnalytics/readme.md
    • ️✔️@azure/cognitiveservices-textanalytics [View full logs]  [Release SDK Changes]
      cmderr	[npmPack] loaded rollup.config.js with warnings
      cmderr	[npmPack] (!) Unused external imports
      cmderr	[npmPack] default imported from external module 'rollup' but never used
      cmderr	[npmPack] ./esm/textAnalyticsClient.js → ./dist/cognitiveservices-textanalytics.js...
      cmderr	[npmPack] created ./dist/cognitiveservices-textanalytics.js in 162ms
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot
    Copy link

    Hi @laramume, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff.

    TaskHow to fixPrioritySupport (Microsoft alias)
    AvocadoFix-AvocadoHighruowan
    Semantic validationFix-SemanticValidation-ErrorHighraychen, jianyxi
    Model validationFix-ModelValidation-ErrorHighraychen,jianyxi
    LintDiffFix-LintDiffhighjianyxi, ruoxuan
    If you need further help, please feedback via swagger feedback."

    Copy link
    Member

    @deyaaeldeen deyaaeldeen left a comment

    Choose a reason for hiding this comment

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

    Looks good for the most part and I did a regeneration in JS with it. However there are a couple issues that I pointed out in my comments.

    "type": "string"
    },
    "loggingOptOut": {
    "default": "true",
    Copy link
    Member

    Choose a reason for hiding this comment

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

    why loggingOptOut is true by default for pii tasks only?

    Copy link
    Contributor Author

    Choose a reason for hiding this comment

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

    for pii sync, pii async, healthcare async this value by default is true because these endpoints usually receive sensitive info and we dont want to log it until customer explicitly says so

    Copy link
    Member

    Choose a reason for hiding this comment

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

    interesting, does logging implies more people will have access to the sensitive data?

    Copy link
    Contributor Author

    Choose a reason for hiding this comment

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

    No only engineering team. We were already logging this for 48 hours but now we have the option to opt out of this 48 hour logging

    Copy link
    Member

    @deyaaeldeen deyaaeldeen left a comment

    Choose a reason for hiding this comment

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

    Thanks for addressing my feedback. However, I tried regenerating off the latest version and I get this error:

    dealmaha@dev:~/text-analytics/sdk/textanalytics/ai-text-analytics$ npx autorest swagger/README.md 
    AutoRest code generation utility [cli version: 3.1.3; node: v14.15.4, max-memory: 4096 MB]
    (C) 2018 Microsoft Corporation.
    https://aka.ms/autorest
    
    There is a new version of AutoRest available (3.1.5).
     > You can install the newer version with with npm install -g autorest@latest
    
       Loading AutoRest core      '/home/dealmaha/.autorest/@autorest_core@3.3.0/node_modules/@autorest/core/dist' (3.3.0)
    INFORMATION: > Loading local AutoRest extension '@autorest/typescript' (/home/dealmaha/corev2-v6)
    INFORMATION: > Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)
      Error: $ref to original location 'https://raw.githubusercontent.com/Azure/azure-rest-api-specs/8ae1f5bb6a6204abf77d7c49a6c4a977747432a2/specification/cognitiveservices/data-plane/TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#/components/schemas/c' is not found in the new refs collection
    

    cc @iscai-msft

    Copy link
    Member

    @deyaaeldeen deyaaeldeen left a comment

    Choose a reason for hiding this comment

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

    Looks good, thanks!

    @maririos
    Copy link
    Member

    @laramume do you have an ETA of when this PR will be merged? We will like to consume it in the SDKs as soon as possible

    @laramume
    Copy link
    Contributor Author

    @laramume do you have an ETA of when this PR will be merged? We will like to consume it in the SDKs as soon as possible

    This PR is good be merged but I dont have permission to do it.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented May 12, 2021

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️⚠️LintDiff: 1 Warnings warning [Detail]
    The following errors/warnings are introduced by current PR:
    Rule Message
    ⚠️ R3017 - GuidUsage Guid used in model definition 'JobMetadata' for property 'jobId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
    Location: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L2129
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️❌Cross-Version Breaking Changes: 34 Errors, 17 Warnings failed [Detail]
    The following breaking changes are detected by comparison with the latest stable version:

    Only 10 items are listed, please refer to log for more details.

    Rule Message
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L361:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L368:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L490:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L497:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L547:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L554:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L604:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L611:11
    1011 - AddingResponseCode The new version adds a response code '400'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L670:11
    1011 - AddingResponseCode The new version adds a response code '500'.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L677:11


    The following breaking changes are detected by comparison with latest preview version:

    Only 10 items are listed, please refer to log for more details.

    Rule Message
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L924:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L889:13
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L903:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L872:13
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L2287:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L2170:13
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L277:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L334:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L391:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L457:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L622:9
    1019 - RemovedEnumValue The new version is removing enum value(s) 'TextElements_v8' from the old version.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L2676:5
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L2559:5
    1027 - DefaultValueChanged The new version has a different default value than the previous one.
    New: TextAnalytics/preview/v3.1-preview.5/TextAnalytics.json#L924:13
    Old: TextAnalytics/preview/v3.1-preview.4/TextAnalytics.json#L889:13
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation

    The following errors/warnings are introduced by current PR:

    |:speech_balloon: AutorestCore/Exception|"readme":"cognitiveservices/data-plane/TextAnalytics/readme.md",
    "tag":"release_3_1_preview.5",
    "details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
    |:speech_balloon: AutorestCore/Exception|"readme":"cognitiveservices/data-plane/TextAnalytics/readme.md",
    "tag":"release_3_1_preview.5",
    "details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
    |:speech_balloon: AutorestCore/Exception|"readme":"cognitiveservices/data-plane/TextAnalytics/readme.md",
    "tag":"release_3_1_preview.5",
    "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|

    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    ghost pushed a commit to Azure/azure-sdk-for-js that referenced this pull request May 12, 2021
    …14808)
    
    - adds support for new text analytics in v3.1-preview.5. Fixes #15128
    - removes the word `batch` to simplify names and avoid confusion after talking with @xirzec and the crew. Fixes #15127
    - add test cases for analyze sentiment and recognize linked entities actions
    - update tests for action validation to match new strict validation behavior in the service in the post request
    - re-enable some disabled tests now that the service fixed those issues
    - disabled the statistics test for `beginAnalyzeActions` because of wrong answers coming from the service and it is currently being investigated
    - the CI failures are because the service did not deploy healthcare API yet so this PR can not be merged until then but please review it.
    - removed the logic for setting model version even if the user does not specify yet. This logic was needed because of a service-side bug that is now fixed. Fixes #14079
    
    [API View](https://apiview.dev/Assemblies/Review/8754191c44914b7e88232f8aba5073de?diffRevisionId=43c78776e4a6490aa4009fb1035ec44d&doc=False&diffOnly=False)
    [Swagger PR](Azure/azure-rest-api-specs#13851)
    @JeffreyRichter JeffreyRichter added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label May 14, 2021
    @mayurid mayurid merged commit 5e1ad2f into Azure:master May 14, 2021
    mkarmark pushed a commit to mkarmark/azure-rest-api-specs that referenced this pull request Jul 21, 2021
    * updated model names in preview version to be consistent with stable version to avoid breaking changes in client side code
    
    * changed swagger files
    
    * new TA API version v3.1-preview.5
    
    * new TA API version v3.1-preview.5
    
    * change input name
    
    * resolve PR comments
    
    * fix PR comments
    
    * change loggingOptOut default value to be string
    
    * change loggingOptOut default value to be string
    
    * change TextElements_v8 to TextElement_v8
    
    * resolve comments
    
    * fix build issues
    
    * fix build issues
    
    * fix build issues
    
    * fix build issues
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 CI-FixRequiredOnFailure
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    9 participants