QueryMilvus 2025.10.9.21

Bundle

com.snowflake.openflow.runtime | runtime-milvus-processors-nar

Description

Queries a given collection in a Milvus database using vectors. Results of query are added to current record under the results record path for each vector searched.

Tags

chatbot, embeddings, gen ai, genai, generative ai, llm, metadata, milvus, openflow, publish, query, search, text, vector

Input Requirement

REQUIRED

Supports Sensitive Dynamic Properties

false

Properties

PropertyDescription
Collection NameThe name of the Milvus collection name to use
Max Query Batch SizeThis is the number of vectors that are contained in a single request to Milvus during a query. Milvus is unable to support batch queries of more then 10 vectors at a time.
Maximum ResultsThe maximum number of results to return (i.e., Top K)
Milvus Connection ServiceConnection Service for accessing Milvus Database
Output Search FieldsComma separated list of additional fields to return from a search against the Milvus database. Milvus will return the score and id fields by default.
PartitionPartition of the vector database that you want to perform operations in. If the database has only one partition leave empty.
Record ReaderThe Record Reader to use for reading the FlowFile
Record WriterThe Record Writer to use for writing the results
Reranking Smoothing ParameterSmoothing Parameter of the Reciprocal Rank Fusion (RRFRanker) during Hybrid Search
Results Record PathSpecifies where in the record to place the results.
Sparse Vector Field NameThe name of the field to use for storing the sparse vectors.
Sparse Vector Indices PathIf, Sparse Vectors are to be provided, this RecordPath points to the indices of the sparse data to use.
Sparse Vector Values PathIf, Sparse Vectors are to be provided, this RecordPath points to the values of the sparse data to use.
Vector Field NameThe name of the field in Milvus to use for storing the vectors.
Vector Record PathThe path to the vector field in the record

Relationships

NameDescription
failureFlowFiles that cannot be sent to Milvus, and for which a retry is not expected to be successful, are routed to this relationship
retryFlowFiles that fail to be sent to Milvus, but for which a retry may help, are routed to this relationship
successFlowFiles that are successfully sent to Milvus are routed to this relationship

See also