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
Copy file name to clipboardExpand all lines: articles/search/retrieval-augmented-generation-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ The decision about which information retrieval system to use is critical because
25
25
26
26
+ Security, global reach, and reliability for both data and operations.
27
27
28
-
+ Integration with LLMs.
28
+
+ Integration with embedding models for indexing, and chat models or languange understanding models for retrieval.
29
29
30
30
Azure AI Search is a [proven solution for information retrieval](/azure/developer/python/get-started-app-chat-template?tabs=github-codespaces) in a RAG architecture. It provides indexing and query capabilities, with the infrastructure and security of the Azure cloud. Through code and other components, you can design a comprehensive RAG solution that includes all of the elements for generative AI over your proprietary content.
Copy file name to clipboardExpand all lines: articles/search/search-get-started-vector.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,14 @@ ms.date: 01/19/2024
14
14
15
15
# Quickstart: Vector search using REST APIs
16
16
17
-
Get started with vector search in Azure AI Search using the **2023-11-01** REST APIs that create, load, and query a search index.
17
+
Get started with vector stores in Azure AI Search using the **2023-11-01** REST APIs that load, and query vectors.
18
18
19
-
Search indexes can have vector and nonvector fields. You can execute pure vector queries, or hybrid queries targeting both vector *and* textual fields configured for filters, sorts, facets, and semantic reranking.
19
+
In Azure AI Search, a *vector store* has an index schema that defines vector and nonvector fields, a vector configuration for algorithms that create the embedding space, and settings on vector field definitions that are used in query requests. The [Create Index](/rest/api/searchservice/indexes/create-or-update) API creates the vector store.
20
+
21
+
You can execute pure vector queries, or hybrid queries targeting both vector *and* textual fields configured for filters, sorts, facets, and semantic reranking.
20
22
21
23
> [!NOTE]
22
-
> The stable REST API version depends on external modules for data chunking and embedding. If you want test-drive the [built-in data chunking and vectorization (public preview)](vector-search-integrated-vectorization.md) features, try the [**Import and vectorize data** wizard](search-get-started-portal-import-vectors.md) for an end-to-end walkthrough.
24
+
> The stable REST API version depends on external solutions for data chunking and embedding. If you want evalulate the [built-in data chunking and vectorization (public preview)](vector-search-integrated-vectorization.md) features, try the [**Import and vectorize data** wizard](search-get-started-portal-import-vectors.md) for an end-to-end walkthrough.
23
25
24
26
## Prerequisites
25
27
@@ -29,7 +31,7 @@ Search indexes can have vector and nonvector fields. You can execute pure vector
29
31
30
32
+ An Azure subscription. [Create one for free](https://azure.microsoft.com/free/).
31
33
32
-
+ Azure AI Search, in any region and on any tier. Most existing services support vector search. For a small subset of services created prior to January 2019, an index containing vector fields will fail on creation. In this situation, a new service must be created.
34
+
+ Azure AI Search, in any region and on any tier. Most existing services support vector search. For a small subset of services created prior to January 2019, an index containing vector fields will fail on creation. In this situation, a new service must be created. You can use the Free tier for this quickstart, but Basic or higher is recommended for larger data files.
33
35
34
36
+ Optionally, for [semantic reranking](semantic-search-overview.md) shown in the last example, your search service must be Basic tier or higher, with [semantic ranking enabled](semantic-how-to-enable-disable.md).
Copy file name to clipboardExpand all lines: articles/search/vector-search-how-to-create-index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,14 @@ ms.date: 01/29/2024
14
14
15
15
# Create a vector store
16
16
17
-
In Azure AI Search, vector data is indexed and stored as *vector fields*in a [search index](search-what-is-an-index.md).
17
+
In Azure AI Search, a *vector store* has an index schema that defines vector and nonvector fields, a vector configuration for algorithms that create the embedding space, and settings on vector field definitions that are used in query requests. The [Create Index](/rest/api/searchservice/indexes/create-or-update) API creates the vector store.
18
18
19
19
Follow these steps to index vector data:
20
20
21
21
> [!div class="checklist"]
22
22
> + Define a schema with one or more vector configurations that specifies algorithms for indexing and search
23
-
> + Add one or more vector fields.
24
-
> + Load the index with vector data [as a separate step](#load-vector-data-for-indexing), or use [integrated vectorization (preview)](vector-search-integrated-vectorization.md) for data chunking and encoding during indexing.
23
+
> + Add one or more vector fields
24
+
> + Load prevectorized data [as a separate step](#load-vector-data-for-indexing), or use [integrated vectorization (preview)](vector-search-integrated-vectorization.md) for data chunking and encoding during indexing.
25
25
26
26
This article applies to the generally available, non-preview version of [vector search](vector-search-overview.md), which assumes your application code calls external resources for chunking and encoding.
0 commit comments