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/search-create-service-portal.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
@@ -74,9 +74,9 @@ Service name requirements:
74
74
75
75
+ Unique within the search.windows.net namespace
76
76
+ Between 2 and 60 characters in length
77
-
+ Consist of lowercase letters, digits, dashes (`-`), or underscores (`_`)
78
-
+ Don't use dashes or underscores in the first 2 characters or as the last single character
79
-
+ Don't use consecutive dashes or underscores anywhere
77
+
+ Consist of lowercase letters, digits, or dashes (`-`)
78
+
+ Don't use dashes in the first 2 characters or as the last single character
79
+
+ Don't use consecutive dashes anywhere
80
80
81
81
> [!TIP]
82
82
> If you have multiple search services, it helps to include the region (or location) in the service name as a naming convention. A name like `mysearchservice-westus` can save you a trip to the properties page when deciding how to combine or attach resources.
Copy file name to clipboardExpand all lines: articles/search/search-get-started-bicep.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
@@ -61,7 +61,7 @@ The Azure resource defined in this Bicep file:
61
61
---
62
62
63
63
> [!NOTE]
64
-
> Replace **\<service-name\>** with the name of the Search service. The service name must only contain lowercase letters, digits, dashes, or underscores. You can't use a dash as the first two characters or the last character. The name has a minimum length of 2 characters and a maximum length of 60 characters.
64
+
> Replace **\<service-name\>** with the name of the Search service. The service name must only contain lowercase letters, digits, or dashes. You can't use a dash as the first two characters or the last character. The name has a minimum length of 2 characters and a maximum length of 60 characters.
65
65
66
66
When the deployment finishes, you should see a message indicating the deployment succeeded.
Copy file name to clipboardExpand all lines: articles/search/vector-search-how-to-query.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,23 +14,23 @@ ms.date: 03/05/2024
14
14
15
15
# Create a vector query in Azure AI Search
16
16
17
-
In Azure AI Search, if you [have vector fields](vector-search-how-to-create-index.md) in a search index, you can follow the instructions in this article to learn how to:
17
+
In Azure AI Search, if you [have vector fields](vector-search-how-to-create-index.md) in a search index, this article explains how to:
18
18
19
19
> [!div class="checklist"]
20
20
> +[Query vector fields](#vector-query-request)
21
21
> +[Filter a vector query](#vector-query-with-filter)
22
22
> +[Query multiple vector fields at once](#multiple-vector-fields)
23
23
> +[Query with integrated vectorization (preview)](#query-with-integrated-vectorization-preview)
24
24
25
-
This article uses REST examples. For code samples in other languages, see the [azure-search-vector-samples](https://github.com/Azure/azure-search-vector-samples) repository for end-to-end workflows that include vector queries.
25
+
This article uses REST examples. For code samples in other languages, see the [azure-search-vector-samples](https://github.com/Azure/azure-search-vector-samples)GitHub repository for end-to-end solutions that include vector queries.
26
26
27
27
## Prerequisites
28
28
29
29
+ Azure AI Search, in any region and on any tier.
30
30
31
31
+[A vector store on Azure AI Search](vector-search-how-to-create-index.md).
32
32
33
-
+ Visual Studio Code with a [REST client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) and sample data if you want to run these examples on your own. This article assumes the stable API version [**2023-11-01**](/rest/api/searchservice/search-service-api-versions?view=rest-searchservice-2023-11-01).
33
+
+ Visual Studio Code with a [REST client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) and sample data if you want to run these examples on your own. See [Quickstart: Create a search index in Azure AI Search using REST](search-get-started-rest.md) for help getting started.
34
34
35
35
> [!TIP]
36
36
> To quickly determine whether your index has vectors, look for fields of type `Collection(Edm.Single)`, with a `dimensions` attribute, and a `vectorSearchProfile` assignment.
@@ -48,12 +48,12 @@ POST https://{{openai-service-name}}.openai.azure.com/openai/deployments/{{opena
48
48
Content-Type: application/json
49
49
api-key: {{admin-api-key}}
50
50
{
51
-
"input": "what azure services support full text search"
51
+
"input": "what azure services support generative AI'"
52
52
}
53
53
```
54
54
55
55
The expected response is 202 for a successful call to the deployed model.
56
-
The "embedding" field in the body of the response is the vector representation of the query string "input". For testing purposes, you would copy the value of the "embedding" array into "vector.value" in a query request, using syntax shown in the next several sections.
56
+
The "embedding" field in the body of the response is the vector representation of the query string "input". For testing purposes, you would copy the value of the "embedding" array into "vectorQueries.vector" in a query request, using syntax shown in the next several sections.
57
57
58
58
The actual response for this POST call to the deployed model includes 1536 embeddings, trimmed here to just the first few vectors for readability.
> The vector query syntax for this version is obsolete in later versions.
166
+
> The vector query syntax for this version is obsolete in later versions. We recommend [upgrading to the latest REST API](search-api-migration.md).
167
167
168
168
[**2023-07-01-Preview**](/rest/api/searchservice/index-preview) first introduced vector query support to [Search Documents](/rest/api/searchservice/preview-api/search-documents). This version added:
169
169
@@ -416,7 +416,7 @@ api-key: {{admin-api-key}}
416
416
417
417
---
418
418
419
-
## Multiple vector fields in a query
419
+
## Multiple vector fields
420
420
421
421
You can set the "vectorQueries.fields" property to multiple vector fields. The vector query executes against each vector field that you provide in the `fields` list. When querying multiple vector fields, make sure each one contains embeddings from the same embedding model, and that the query is also generated from the same embedding model.
422
422
@@ -445,7 +445,7 @@ api-key: {{admin-api-key}}
445
445
}
446
446
```
447
447
448
-
## Multiple vector queries in parallel
448
+
## Multiple vector queries
449
449
450
450
Multi-query vector search sends multiple queries across multiple vector fields in your search index. A common example of this query request is when using models such as [CLIP](https://openai.com/research/clip) for a multimodal vector search where the same model can vectorize image and text content.
451
451
@@ -492,7 +492,7 @@ Search results would include a combination of text and images, assuming your sea
492
492
493
493
## Query with integrated vectorization (preview)
494
494
495
-
This section shows a vector query that invokes the new [integrated vectorization](vector-search-integrated-vectorization.md) preview feature. Use [**2023-10-01-Preview** REST API](/rest/api/searchservice/documents/search-post?view=rest-searchservice-2023-10-01-preview&preserve-view=true) or an updated beta Azure SDK package.
495
+
This section shows a vector query that invokes the new [integrated vectorization](vector-search-integrated-vectorization.md) preview feature that converts a text query into a vector. Use [**2023-10-01-Preview** REST API](/rest/api/searchservice/documents/search-post?view=rest-searchservice-2023-10-01-preview&preserve-view=true) or an updated beta Azure SDK package.
496
496
497
497
A prerequisite is a search index having a [vectorizer configured and assigned](vector-search-how-to-configure-vectorizer.md) to a vector field. The vectorizer provides connection information to an embedding model used at query time.
498
498
@@ -573,7 +573,7 @@ The examples in this article used a "select" statement to specify text (nonvecto
573
573
> [!NOTE]
574
574
> Vectors aren't designed for readability, so avoid returning them in the response. Instead, choose non-vector fields that are representative of the search document. For example, if the query targets a "descriptionVector" field, return an equivalent text field if you have one ("description") in the response. -->
575
575
576
-
## Number of ranked results in a vector query response
576
+
## Quantity of ranked results in a vector query response
577
577
578
578
A vector query specifies the `k` parameter, which determines how many matches are returned in the results. The search engine always returns `k` number of matches. If `k` is larger than the number of documents in the index, then the number of documents determines the upper limit of what can be returned.
579
579
@@ -588,7 +588,7 @@ Query parameters affecting result count include:
588
588
589
589
Both "k" and "top" are optional. Unspecified, the default number of results in a response is 50. You can set "top" and "skip" to [page through more results](search-pagination-page-layout.md#paging-results) or change the default.
0 commit comments