You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Step 2: Upload local files to your project Azure Blob Storage container
28
-
We will upload the local file to your project Azure Blob Storage container. This is the same storage account you connected to your agent during the agent setup.
29
-
The project asset ID is the URI of the uploaded file and we print out this value. If you create more agents in the same project that want to use the uploaded file, you can reuse this asset ID. That way you don't need to upload the file again.
28
+
We upload the local file to your project Azure Blob Storage container. This is the same storage account you connected to your agent during the agent setup.
29
+
The project asset ID is the URI of the uploaded file and we print this value. If you create more agents in the same project that want to use the uploaded file, you can reuse this asset ID. That way you don't need to upload the file again.
30
30
```python
31
-
# We will upload the local file to your project Azure Blob Storage container and will use it for vector store creation.
31
+
# We'll upload the local file to your project Azure Blob Storage container and will use it for vector store creation.
### Step 4: Create second vector store using the previously uploaded file
78
-
Now we will create a second vector store using the previously uploaded file. This is useful if you have multiple agents that need access to the same files.
78
+
Now we create a second vector store using the previously uploaded file. Using the asset_uri of file already in Azure Blob Storage is useful if you have multiple agents that need access to the same files. That way you don't need to upload the same file multiple times.
79
79
```python
80
80
81
81
# create a vector store with a previously uploaded file and wait for it to be processed
0 commit comments