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 property semanticSearch for Search Service #3874

Closed
dombajova opened this issue Jan 20, 2025 · 2 comments
Closed

Add property semanticSearch for Search Service #3874

dombajova opened this issue Jan 20, 2025 · 2 comments
Assignees
Labels
kind/enhancement Improvements or new features resolution/by-design This issue won't be fixed because the functionality is working as designed

Comments

@dombajova
Copy link

Hello!

When creating Search Service manually or through azure REST API it is possible to define whether semanticSearch should be enabled and select a plan.

See https://learn.microsoft.com/en-us/rest/api/searchmanagement/services/create-or-update?view=rest-searchmanagement-2023-11-01&tabs=HTTP#searchsemanticsearch

Issue details

Add support for this property to ServiceArgs.

Affected area/feature

Search Service create and update

@dombajova dombajova added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Jan 20, 2025
@thomas11
Copy link
Contributor

thomas11 commented Jan 20, 2025

Hi @dombajova, we already support it, but the default API version 2022-09-01 is too old to have it. You can explicitly import a newer one, e.g., latest stable 2023-11-01 has it.

The import depends on your programming language, in C# for example instead of AzureNative.Search you would use AzureNative.Search.V20231101.

Unfortunately, we can only bump the default API versions in new major versions of the provider since there could be breaking changes.

@thomas11 thomas11 removed the needs-triage Needs attention from the triage team label Jan 20, 2025
@dombajova
Copy link
Author

Thank you for letting me know :)

@thomas11 thomas11 added the resolution/by-design This issue won't be fixed because the functionality is working as designed label Jan 27, 2025
@thomas11 thomas11 self-assigned this Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/by-design This issue won't be fixed because the functionality is working as designed
Projects
None yet
Development

No branches or pull requests

2 participants