You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ability to use more than one Azure AI Search Index in LibreChat, e. g. with modelSpecs.
More details
An Azure AI Search indexes is usually built across a certain collection of data (documents).
Therefore it is common practise to have more than one index which can then be connected to an LLM as a search resource.
Currently, LibreChat supports only one specific Azure AI Search Index through the .env file.
Maybe it would be possible to provide multivalues for these params, e. g.:
Ideally even more than one Search Service Endpoint could be configured but more than one index would already be a huge benefit. The ability to configure more than one Search Service would imply that the index names have to be assigned to their service and there would also be more than one Search API key.
Multiple indexes could then be combined with different modelSpecs as with the rework for plugins discussed in 3607 or some other way to select the desired index.
Which components are impacted by your request?
Endpoints
Pictures
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What features would you like to see added?
Ability to use more than one Azure AI Search Index in LibreChat, e. g. with modelSpecs.
More details
An Azure AI Search indexes is usually built across a certain collection of data (documents).
Therefore it is common practise to have more than one index which can then be connected to an LLM as a search resource.
Currently, LibreChat supports only one specific Azure AI Search Index through the
.env
file.Maybe it would be possible to provide multivalues for these params, e. g.:
AZURE_AI_SEARCH_SERVICE_ENDPOINT=https://ai-search-service1.search.windows.net
AZURE_AI_SEARCH_INDEX_NAME=ai-index-1,ai-index-2,ai-index-3
AZURE_AI_SEARCH_API_KEY=abcdefghijklmnopqrstuvwxyz
Ideally even more than one Search Service Endpoint could be configured but more than one index would already be a huge benefit. The ability to configure more than one Search Service would imply that the index names have to be assigned to their service and there would also be more than one Search API key.
Multiple indexes could then be combined with different modelSpecs as with the rework for plugins discussed in 3607 or some other way to select the desired index.
Which components are impacted by your request?
Endpoints
Pictures
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: