Skip to content

Commit 9ba4d43

Browse files
committed
Naming changes
1 parent a793366 commit 9ba4d43

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

Labs/lab_3_mongodb_vector_search.ipynb

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"cell_type": "markdown",
55
"metadata": {},
66
"source": [
7-
"# Vector Search using Azure Cosmos DB API for MongoDB\n",
7+
"# Vector Search using vCore-based Azure Cosmos DB for MongoDB\n",
88
"\n",
99
"This notebook demonstrates using an Azure OpenAI embedding model to vectorize documents already stored in Azure Cosmos DB API for MongoDB, storing the embedding vectors and the creation of a vector index. Lastly, the notebook will demonstrate how to query the vector index to find similar documents.\n",
1010
"\n",
@@ -120,7 +120,7 @@
120120
" '''\n",
121121
" response = ai_client.embeddings.create(input=text, model=EMBEDDINGS_DEPLOYMENT_NAME)\n",
122122
" embeddings = response.data[0].embedding\n",
123-
" time.sleep(0.5) # rest period to avoid rate limiting on AOAI for free tier\n",
123+
" time.sleep(0.5) # rest period to avoid rate limiting on AOAI\n",
124124
" return embeddings"
125125
]
126126
},
@@ -270,9 +270,9 @@
270270
"cell_type": "markdown",
271271
"metadata": {},
272272
"source": [
273-
"## Use vector search in Azure Cosmos DB API for MongoDB vCore\n",
273+
"## Use vector search in vCore-based Azure Cosmos DB for MongoDB\n",
274274
"\n",
275-
"Now that each document has its associated vector embedding and the vector indexes have been created on each collection, we can now use the vector search capabilities of Azure Cosmos DB API for MongoDB vCore."
275+
"Now that each document has its associated vector embedding and the vector indexes have been created on each collection, we can now use the vector search capabilities of vCore-based Azure Cosmos DB for MongoDB."
276276
]
277277
},
278278
{

Labs/lab_4_langchain.ipynb

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -76,9 +76,9 @@
7676
"source": [
7777
"## Vector search with LangChain\n",
7878
"\n",
79-
"In the previous lab, the `pymongo` library was used to perform a vector search through a db command to find product documents that were most similar to the user's input. In this lab, you will use the `langchain` library to perform the same search. LangChain has a vector store class named **AzureCosmosDBVectorSearch**, a community contribution, that supports vector search in Azure CosmosDB for MongoDB API vCore.\n",
79+
"In the previous lab, the `pymongo` library was used to perform a vector search through a db command to find product documents that were most similar to the user's input. In this lab, you will use the `langchain` library to perform the same search. LangChain has a vector store class named **AzureCosmosDBVectorSearch**, a community contribution, that supports vector search in vCore-based Azure Cosmos DB for MongoDB.\n",
8080
"\n",
81-
"When establishing the connection to the vector store (MongoDB vCore), recall that in previous labs the products collection was populated and a contentVector field added that contains the vectorized embeddings of the document itself. Finally, a vector index was also created on the contentVector field to enable vector search. The vector index in each collection is named `VectorSearchIndex`.\n",
81+
"When establishing the connection to the vector store (vCore-based Azure Cosmos DB for MongoDB), recall that in previous labs the products collection was populated and a contentVector field added that contains the vectorized embeddings of the document itself. Finally, a vector index was also created on the contentVector field to enable vector search. The vector index in each collection is named `VectorSearchIndex`.\n",
8282
"\n",
8383
"The return value of a vector search in LangChain is a list of `Document` objects. The LangChain `Document` class contains two properties: `page_content`, that represents the textual content that is typically used to augment the prompt, and `metadata` that contains all other attributes of the document. In the cell below, we'll use the `_id` field as the page_content, and the rest of the fields are returned as metadata.\n",
8484
"\n",
@@ -272,7 +272,7 @@
272272
"metadata": {},
273273
"outputs": [],
274274
"source": [
275-
"# Create tools that will use vector search in the Azure Cosmos DB for MongoDB vCore collections\n",
275+
"# Create tools that will use vector search in vCore-based Azure Cosmos DB for MongoDB collections\n",
276276
"\n",
277277
"# create a chain on the retriever to format the documents as JSON\n",
278278
"products_retriever_chain = products_retriever | format_docs\n",

Labs/lab_5_backend_api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Lab 5 - Backend API
1+
# Backend API
22

33
In the previous lab, a LangChain agent was created armed with tools to do vector lookups and concrete document id lookups via function calling. In this lab, the agent functionality needs to be extracted into a backend api for the frontend application that will allow users to interact with the agent.
44

@@ -231,4 +231,4 @@ The last step is to deploy the backend api container image to Azure Container Ap
231231
232232
18. Repeat steps 8-10 from the [Run the backend api locally section](#run-the-backend-api-locally) to test the backend api running in a container on Azure Container Apps.
233233
234-
Congratulations! You have successfully deployed the backend api to Azure Container Apps where it is ready to service the frontend application.
234+
Congratulations on the successful deployment of the backend api to Azure Container Apps where it is ready to service the frontend application.

0 commit comments

Comments
 (0)