Closed vanzegbroecke closed 1 month ago
Thank you for your feedback. Tagging and routing to the team member best able to assist.
Hi @vanzegbroecke. Thanks for reaching out and we regret that you're experiencing difficulties. The reason that index aliases were removed for the v11.6.0 release is because they are a preview feature that is not supported in the stable version of the Azure Search service. This is discussed in Create an index alias in Azure AI Search and detailed in the REST API documentation Aliases - Create Or Update
A stable version of the client library is unable to depend on a preview version of the service. Should the feature progress to stable and support is added to the Search service, the client library will also support it. Likewise, should the feature continue to exist in the preview version of the Search service, the next preview release of the client library will support it.
Please be aware that our beta releases should be considered unstable and potentially disruptive changes should be expected from release-to-release. We do not guarantee that the public API will not change in our beta releases nor are those changes considered breaking. Our stable releases, on the other hand, do follow the .NET Breaking Change Rules per the Azure Design Guidelines.
Hi @vanzegbroecke. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.
Hi @vanzegbroecke, since you haven’t asked that we /unresolve
the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve
to reopen the issue.
Library name and version
Azure.Search.Documents 11.6.0
Query/Question
Could you please explain to me what the reasoning is behind removing index aliases from version 11.6.0?
What is the proposed approach to rebuild an index without index aliases and without downtime?
Environment
No response