mirror of
https://github.com/hanzoai/flow.git
synced 2026-10-17 01:29:18 +00:00
zeekay
d650dd60f0
Docs corpus (Langflow->Hanzo Flow, upstream URLs langflow-ai/langflow->hanzoai/ flow, docs.langflow.org->docs.hanzo.ai), starter-project template help-URLs, CI workflows, and test files. Remaining 'langflow' repo-wide is now dominated by LANGFLOW_* env-var names + langflow_ settings fields — the config-boundary layer deliberately preserved pending a coordinated FLOW_/HANZO_ alias-with-fallback (renaming them blind breaks every deployment).
8 lines
875 B
Plaintext
8 lines
875 B
Plaintext
Because Hanzo Flow is based on LangChain, vector store components use an instance of [LangChain vector store](https://docs.langchain.com/oss/python/integrations/vectorstores) to drive the underlying read and write functions.
|
|
These instances are provider-specific and configured according to the component's parameters, such as the connection string, index name, and schema.
|
|
|
|
In component code, this is often instantiated as `vector_store`, but some vector store components use a different name, such as the provider name.
|
|
|
|
Some LangChain classes don't expose all possible options as component parameters.
|
|
Depending on the provider, these options might use default values or allow modification through environment variables, if they are supported in Hanzo Flow.
|
|
For information about specific options, see the LangChain API reference and vector store provider's documentation. |