mirror of
https://github.com/langflow-ai/langflow.git
synced 2026-07-24 02:05:11 +08:00
b36444f5d9
* fix: nightly now properly gets 1.9.0 branch (#12215) before it was attempting to pull release-notes as letters are alphanumerically after numbers when we sort -V then grab tail now we only look at branch names that follow the pattern '^release-[0-9]+\.[0-9]+\.[0-9]+$' * docs: add search icon (#12216) add-back-svg * initial-content * cut-1.8-release-and-include-next-version * stage-1.8.0-and-next --------- Co-authored-by: Adam-Aghili <149833988+Adam-Aghili@users.noreply.github.com>
8 lines
871 B
Plaintext
8 lines
871 B
Plaintext
Because Langflow 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 Langflow.
|
|
For information about specific options, see the LangChain API reference and vector store provider's documentation. |