- Issue created by @damienmckenna
- 🇺🇸United States damienmckenna NH, USA
It might be best to have a selector to choose the engine that is used, e.g. "faiss" or "lucene".
FWIW manually changing it to "faiss" lets it save without errors.
It isn't possible to save a Search API using Opensearch as the AI backend, it gives this error:
An error occurred: "OpenSearch error: mapper_parsing_exception - Failed to parse mapping [_doc]: nmslib engine is deprecated in OpenSearch and cannot be used for new index creation in OpenSearch from 3.0.0. - Request: PUT http://opensearch:9200/mysite_ai - Body: {"settings":{"index":{"number_of_shards":1,"number_of_replicas":1,"knn":true,"max_result_window":20000}},"mappings":{"properties":{"vector":{"type":"knn_vector","dimension":2,"method":{"name":"hnsw","space_type":"innerproduct","engine":"nmslib","parameters":{"ef_construction":128,"m":16}}}}}}"
Set up OpenSearch 3 on the server.
Go through the process to set up a index.
When saving an AI search_api index with OpenSearch, it will fail.
Make the module compatible with Opensearch 3.
Fix the API issues.
TBD
TBD
TBD
Active
1.0
Code
It might be best to have a selector to choose the engine that is used, e.g. "faiss" or "lucene".
FWIW manually changing it to "faiss" lets it save without errors.