Deep Lake Vector Store API
Running Vector Search in the Deep Lake Vector Store module.
Search Options for Deep Lake Vector Stores in the Deep Lake API
This tutorial requires installation of:
Vector Search Using Python Logic (Client-Side)
Let's load the same vector store used in the Quickstart and run embeddings search based on a user prompt using the Deep Lake Vector Store module.
Next, let's define an embedding function using OpenAI. It must work for a single string and a list of strings, so that it can both be used to embed a prompt and a batch of texts.
Simple Vector Search
Lets run a simple vector search using default options, which performs simple cosine similarity search in Python on the client.
The search_results
is a dictionary with keys for the text
, score
, id
, and metadata
, with data ordered by score. By default, it returns 4 samples ordered by similarity score, and if we examine the first returned text, it appears to contain the text about trust and safety models that is relevant to the prompt.
Returns:
Advanced Vector Search
Vector search can be combined with other search logic for performing more advanced queries. Let's define a function compatible with deeplake.filter for filtering data prior to the vector search. The function below will filter samples that contain the word "program"
in the text
tensor.
Let's run the vector search with the filter above, return more samples (k = 10
), and perform similarity search using L2 metric (distance_metric = "l2"
):
We can verity that the word "program"
is present in all of the results:
Vector Search Using Compute Engine (Client-Side)
Deep Lake offers advanced search features using Compute Engine, which executes queries with higher performance in C++, and offers querying using Deep Lake's Tensor Query Language (TQL).
In order to use Compute Engine, Deep Lake data must be stored in Deep Lake Storage, or in the user's cloud while being connected to Deep Lake using Managed Credentials.
Let's load a larger Vector Store for running more interesting queries:
NOTE: this Vector Store is stored in us-east
, and query performance may vary significantly depending on your location. In real-world use-cases, users would store their vector stores in regions optimized for their use case.
Simple Vector Search
Lets run a simple vector search and specify exec_option = "compute_engine"
, which will performs cosine similarity search using Compute Engine on the client.
If we examine the first returned text, it appears to contain the text about trust and safety models that is relevant to the prompt.
Returns:
Advanced Vector Search
Now let's run a more advanced search that includes filtering of text
, metadata
, and embedding
tensors. We do this using TQL by combining embedding search syntax (cosine_similarity(embedding, ...)
) and filtering syntax (where ....
).
We are interested in answering a prompt based on the question:
Therefore, we apply a filter to only search for text
that contains the word "python"
and metadata
where the source
key contains ".py"
.
Vector Search Using the Managed Tensor Database (Server-Side)
Any of the queries above can be executed on the Managed Tensor Database (instead of the client) by specifying exec_option = "tensor_db".
Note that these queries are only available for dataset stored in the Managed Tensor Database, which is done by specifying vector_store_path = hub://org_id/dataset_name
and runtime = {"tensor_db": True}
during Vector Store creation.
If Vector Stores are not in the Managed Tensor Database, they can be migrated using these steps:
Last updated