Skip to main content

Milvus

Bundles contain custom components that support specific third-party integrations with Langflow.

This page describes the components that are available in the Milvus bundle.

Milvus vector store

The Milvus component reads and writes to Milvus vector stores using an instance of Milvus vector store.

About vector store instances

Because Langflow is based on LangChain, vector store components use an instance of LangChain vector store 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.

If you use a vector store component to query your vector database, it produces search results that you can pass to downstream components in your flow as a list of Data objects or a tabular DataFrame. If both types are supported, you can set the format near the vector store component's output port in the visual editor.

tip

For a tutorial using a vector database in a flow, see Create a vector RAG chatbot.

Milvus vector store parameters

You can inspect a vector store component's parameters to learn more about the inputs it accepts, the features it supports, and how to configure it.

Some parameters are hidden by default in the visual editor. You can modify all parameters through the Controls in the component's header menu.

Some parameters are conditional, and they are only available after you set other parameters or select specific options for other parameters. Conditional parameters may not be visible on the Controls pane until you set the required dependencies.

For information about accepted values and functionality, see the Milvus documentation or inspect component code.

NameTypeDescription
collection_nameStringInput parameter. Name of the Milvus collection.
collection_descriptionStringInput parameter. Description of the Milvus collection.
uriStringInput parameter. Connection URI for Milvus.
passwordSecretStringInput parameter. Password for Milvus.
usernameSecretStringInput parameter. Username for Milvus.
batch_sizeIntegerInput parameter. Number of data to process in a single batch.
search_queryStringInput parameter. Query for similarity search.
ingest_dataDataInput parameter. Data to be ingested into the vector store.
embeddingEmbeddingsInput parameter. Embedding function to use.
number_of_resultsIntegerInput parameter. Number of results to return in search.
search_typeStringInput parameter. Type of search to perform.
search_score_thresholdFloatInput parameter. Minimum similarity score for search results.
search_filterDictInput parameter. Metadata filters for search query.
setup_modeStringInput parameter. Configuration mode for setting up the vector store.
vector_dimensionsIntegerInput parameter. Number of dimensions of the vectors.
pre_delete_collectionBooleanInput parameter. Whether to delete the collection before creating a new one.
Search