Skip to content

Commit 218699b

Browse files
committed
more edits
1 parent 3ce70e4 commit 218699b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/search/search-howto-reindex.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,9 +131,9 @@ The order of operations is:
131131

132132
1. [Drop the existing index](/rest/api/searchservice/indexes/delete). queries targeting the index are immediately dropped. Remember that deleting an index is irreversible, destroying physical storage for the fields collection and other constructs.
133133

134-
1. [Post a revised index](/rest/api/searchservice/indexes/create), where the body of the request includes changed or modified field definitions.
134+
1. [Post a revised index](/rest/api/searchservice/indexes/create), where the body of the request includes changed or modified field definitions and configurations.
135135

136-
1. [Load the index with documents](/rest/api/searchservice/documents) from an external source.
136+
1. [Load the index with documents](/rest/api/searchservice/documents) from an external source. Documents are indexed using the field definitions and configurations of the new schema.
137137

138138
When you create the index, physical storage is allocated for each field in the index schema, with an inverted index created for each searchable field and a vector index created for each vector field. Fields that aren't searchable can be used in filters or expressions, but don't have inverted indexes and aren't full-text or fuzzy searchable. On an index rebuild, these inverted indexes and vector indexes are deleted and recreated based on the index schema you provide.
139139

0 commit comments

Comments
 (0)