Skip to content

Commit a312e9b

Browse files
committed
still fixing links
1 parent f41b88f commit a312e9b

File tree

3 files changed

+10
-9
lines changed

3 files changed

+10
-9
lines changed

articles/ai-services/agents/how-to/tools/azure-ai-search.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Use an existing Azure AI Search index with the agent's Azure AI Search tool.
3333
**Index with semantic configuration**
3434
- By default, the Azure AI Search tool runs hybrid + semantic search on all text fields.
3535

36-
<a id="overview"></a>
36+
<a id="overview-pivot"></a>
3737

3838
[!INCLUDE [setup](../../includes/azure-search/setup.md)]
3939

articles/ai-services/agents/includes/azure-search/code-examples.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 12/10/2024
1111
This quickstart shows how to use an existing Azure AI Search index with the Azure AI Search tool.
1212

1313
### Prerequisites
14-
Complete the [Azure AI Search tool setup](../../how-to/tools/azure-ai-search.md#overview).
14+
Complete the [Azure AI Search tool setup](../../how-to/tools/azure-ai-search.md#overview-pivot).
1515

1616
### Step 1: Create an Azure AI Client
1717
First, create an Azure AI Client using the connection string of your project.

articles/ai-services/agents/includes/file-search/deep-dive.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
1-
1+
---
2+
manager: nitinme
3+
author: fosteramanda
4+
ms.author: fosteramanda
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 12/10/2024
8+
---
29
## Creating vector stores and adding files
310

411
You can create a vector store and add files to it in a single API call:
@@ -67,12 +74,6 @@ project_client.agents.delete_vector_store(vector_store.id)
6774
print("Deleted vector store")
6875
```
6976

70-
## Ensuring vector store readiness before creating runs
71-
72-
We highly recommend that you ensure all files in a vector_store are fully processed before you create a run. This approach ensures that all the data in your vector store is searchable. You can check for vector store readiness by using the polling helpers in the SDKs, or by manually polling the `vector_store` object to ensure the status is completed.
73-
74-
As a fallback, there's a 60-second maximum wait in the run object when the thread's vector store contains files that are still being processed. This step ensures that any files your users upload in a thread are fully searchable before the run proceeds. This fallback wait does not apply to the agent's vector store.
75-
7677
## Managing costs with expiration policies
7778

7879
For basic agent setup, the `file_search` tool uses the `vector_stores` object as its resource and you are billed based on the size of the vector_store objects created. The size of the vector store object is the sum of all the parsed chunks from your files and their corresponding embeddings.

0 commit comments

Comments
 (0)