Qdrant
Unstable API
0.8.0
@project-lakechain/qdrant-storage-connector
The Qdrant storage connector enables uploading vector embeddings produced by other middlewares to a Qdrant collection.
âšī¸ This middleware interacts with a third-party API outside of your AWS account.
đ˛ Adding Documents
To use the Qdrant storage connector, you import it in your CDK stack, and connect it to a data source providing document embeddings.
đ You need to specify a Qdrant API key to the connector, by specifying a reference to an AWS Secrets Manager secret containing the API key.
Store Text
When the document being processed is a text document, you can choose to store the text of the document in the Qdrant payload. To do so, you can use the withStoreText
and withTextKey
options. If the document is not a text, this option is ignored.
đ By default, the text is not included in the index.
Configure Named vector
Since Qdrant supports multiple vectors per entry, you can use the withVectorName
option to specify one.
The connector defaults to unnamed (default) vector.
đ By default, the text is not included in the index.
đˇī¸ Properties
Supported Inputs
Mime Type | Description |
---|---|
*/* | This middleware supports any type of documents. Note that if no embeddings are specified in the document metadata, the document is filtered out. |
Supported Outputs
This middleware does not produce any output.
Supported Compute Types
Type | Description |
---|---|
CPU | This middleware only supports CPU compute. |
đ Examples
- Bedrock + Qdrant Pipeline - An example showcasing an embedding pipeline using Amazon Bedrock and Qdrant.