Configurable index name#906
Conversation
|
Would this be set on the Settings page or the TUI? If they can set it in the |
|
Will be closed by #914 . Could you please check if that PR has all you need? |
I see, sounds good. The changes to the settings page are not mandatory, can be removed. The main thing needed for easy benchmarking of the system is the option to change the index name "on-the-fly" while the system runs, programmatically via the backend API. This is what i tried to do here .. Let me know if that makes sense .. |
…e_index_name add a load of the env variable OPENSEARCH_INDEX_NAME into the config index_name
|
Merging forcefully since integration tests are failing because OpenAI keys are not present in external repos. |
Convert INDEX_NAME to a configurable parameter
This allows benchmarking multiple setups with separated indices.
The index name can be changed via the settings endpoint.
Also added an option to change from the frontend - but can be removed if this is not something that should be exposed to the user.
Detailed changes (AI-generated):
Backend Changes:
config_manager.py: Added
index_name: str = "documents"field toKnowledgeConfigdataclassconfig/settings.py: Removed
INDEX_NAMEconstant and addedget_index_name()function to retrieve from configUpdated all files using INDEX_NAME: Replaced constant with
get_index_name()function call in:api/settings.py:
index_nameto GET responseservices/flows_service.py: Added
update_flows_index_name()method to update the OpenSearch components in Langflowutils/telemetry/message_id.py: Added
ORB_SETTINGS_INDEX_NAME_UPDATEDtelemetry eventFrontend Changes:
index_name?: stringtoKnowledgeSettingsinterfaceindex_name?: stringtoUpdateSettingsRequestinterfaceindexNamehandleIndexNameChange()handler with debounced updatesSummary:
The index name can now be:
knowledge.index_name