Azure / Azure/azure-search-vector-samples
Could not complete vectorization action. Could not reach the vectorization endpoint.
- Dominant language
- Jupyter Notebook
- Stars
- 910
- Forks
- 377
- PR merge metrics
- No merged PRs in 30d
Description
Hello
@farzad528
We have properly created indexes, indexers, data sources and skillsets and the indexers are working properly and we get document chunks in the index.
However we get this error:
"Could not complete vectorization action. Could not reach the vectorization endpoint."
If we disable vector search in the query options, we can see the index content and the vector values without any problem.
We are using version: 2023-10-01-Preview
If we try: 2023-11-01 then we get this error:
"The request is invalid. Details: The parameter 'queryLanguage' in the request payload is not a valid parameter for the operation 'search'
We are using Azure Search Explorer for this testing.
PD: On this notebook: https://github.com/Azure/azure-search-vector-samples/blob/main/demo-python/code/azure-search-integrated-vectorization-sample.ipynb
You mentioned: **This sample currently uses version 11.4.0b12 which is a pre-release version. Please note, that integrated vectorization feature is in preview and has not been published to [azure-search-documents](https://pypi.org/project/azure-search-documents/#description) on pypi.**
We used 11.4.0.b9 in a different tenant and search service and it worked without any problem. Also I see on pypi that 11.4.b012 is not even there (https://pypi.org/project/azure-search-documents/#history) but 11.4.0 is released. I assume that this notebook is just outdated?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with demo-python/code/azure-search-integrated-vectorization-sample.ipynb and reproduce the report using Azure Search Explorer. Compare the 2023-10-01-Preview and 2023-11-01 API versions with the mentioned azure-search-documents SDK versions. Done means identifying the cause of the vectorization endpoint error and documenting the compatible sample and version combination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, jupyter-notebook, python
- Domain
- cloud, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100