Skip to content

Commit abad7f4

Browse files
committed
Updated vector content
1 parent 7f07488 commit abad7f4

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

articles/search/vector-search-overview.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,18 @@ ms.service: azure-ai-search
99
ms.custom:
1010
- ignite-2023
1111
ms.topic: conceptual
12-
ms.date: 05/08/2025
12+
ms.date: 06/17/2025
1313
---
1414

15-
# Vectors in Azure AI Search
15+
# Vector search in Azure AI Search
1616

17-
Vector search is an approach in information retrieval that supports indexing and query execution over numeric representations of content. Because the content is numeric rather than plain text, matching is based on vectors that are most similar to the query vector, which enables matching across:
17+
Vector search is an information retrieval approach that supports indexing and querying over numeric representations of content. Because the content is numeric rather than plain text, matching is based on vectors that are most similar to the query vector, which enables matching across:
1818

19-
+ semantic or conceptual likeness ("dog" and "canine", conceptually similar yet linguistically distinct)
20-
+ multilingual content ("dog" in English and "hund" in German)
21-
+ multiple content types ("dog" in plain text and a photograph of a dog in an image file)
19+
+ Semantic or conceptual likeness. For example, "dog" and "canine" are conceptually similar but linguistically distinct.
20+
+ Multilingual content, such as "dog" in English and "hund" in German.
21+
+ Multiple content types, such as "dog" in plain text and an image of a dog.
2222

23-
This article provides [a high-level introduction to vector support](#vector-search-concepts) in Azure AI Search. It also explains integration with other Azure services and covers [terminology and concepts](#vector-search-concepts) related to vector search development.
23+
This article provides a high-level introduction to vector support in Azure AI Search. It also explains integration with other Azure services and covers [terminology and concepts](#vector-search-concepts) related to vector search development.
2424

2525
We recommend this article for background, but if you'd rather get started, follow these steps:
2626

@@ -29,7 +29,7 @@ We recommend this article for background, but if you'd rather get started, follo
2929
> + [Create a vector index](vector-search-how-to-create-index.md)
3030
> + [Run vector queries](vector-search-how-to-query.md)
3131
32-
You could also begin with the [vector quickstart](search-get-started-vector.md) or the [code samples on GitHub](https://github.com/Azure/azure-search-vector-samples).
32+
You can also begin with the [vector quickstart](search-get-started-vector.md) or the [code samples on GitHub](https://github.com/Azure/azure-search-vector-samples).
3333

3434
## What scenarios can vector search support?
3535

articles/search/vector-store.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,9 @@ This article covers the key concepts for creating and managing a vector index, i
3131

3232
Azure AI Search supports two patterns for vector retrieval:
3333

34-
+ **Classic search.** After users enter queries into a search bar, your application code or the search engine vectorizes the input and performs a vector search over the vector fields in your index. The search engine returns results as a flattened row set, and you can choose which fields to include in the response. Because there's no chat model or extra reasoning, you should include nonvector fields in your index to present human-readable results to users. For more information, see [Create a vector query](vector-search-how-to-query.md) and [Create a hybrid query](hybrid-search-how-to-query.md).
34+
+ **Classic search**. After users enter queries into a search bar, your application code or the search engine vectorizes the input and performs a vector search over the vector fields in your index. The search engine returns results as a flattened row set, and you can choose which fields to include in the response. Because there's no chat model or extra reasoning, you should include nonvector fields in your index to present human-readable results to users. For more information, see [Create a vector query](vector-search-how-to-query.md) and [Create a hybrid query](hybrid-search-how-to-query.md).
3535

36-
+ **Generative search.** Language models use data from Azure AI Search to respond to user queries. An orchestration layer typically coordinates prompts and maintains context, feeding search results into chat models like GPT. This pattern is based on the [retrieval-augmented generation (RAG)](retrieval-augmented-generation-overview.md) architecture, where the search index supplies grounding data.
36+
+ **Generative search**. Language models use data from Azure AI Search to respond to user queries. An orchestration layer typically coordinates prompts and maintains context, feeding search results into chat models like GPT. This pattern is based on the [retrieval-augmented generation (RAG)](retrieval-augmented-generation-overview.md) architecture, where the search index supplies grounding data.
3737

3838
## Schema of a vector index
3939

@@ -85,7 +85,7 @@ Vector indexes require more than just vector fields. For example, all indexes mu
8585
]
8686
```
8787

88-
Other fields, such as `content`, provide the human-readable equivalent of the `content_vector` field. If you're using language models exclusively for response formulation, you can omit nonvector content fields, but solutions that push search results directly to client apps should have nonvector content.
88+
Other fields, such as the `content` field, provide the human-readable equivalent of the `content_vector` field. If you're using language models exclusively for response formulation, you can omit nonvector content fields, but solutions that push search results directly to client apps should have nonvector content.
8989

9090
Metadata fields are useful for filters, especially if they include origin information about the source document. Although you can't filter directly on a vector field, you can set prefilter or postfilter modes to filter before or after vector query execution.
9191

0 commit comments

Comments
 (0)