Skip to content

Commit 3974ab5

Browse files
committed
indentation bug
1 parent ce6d5a1 commit 3974ab5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/search/search-how-to-create-search-index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Write permissions are required for creating and loading indexes, granted through
2424

2525
Index creation is largely a schema definition exercise. Before creating one, you should have:
2626

27-
+ A clear idea of which fields you want to make searchable, retrievable, filterable, facetable, and sortable in your index (discussed in [schema checklist](#schema-checklist)).
27+
+ A clear idea of which fields you want to make searchable, retrievable, filterable, facetable, and sortable in your index (more about this is discussed in [schema checklist](#schema-checklist)).
2828

2929
+ A unique identifier in source data that can be used as the document key (or ID) in the index.
3030

@@ -64,7 +64,7 @@ Use this checklist to help drive the design decisions for your search index.
6464

6565
1. Identify one field in the source data that contains unique values, allowing it to function as the key field in your index. For example, if you're indexing from Blob Storage, the storage path is often used as the document key.
6666

67-
Every index requires one field that serves as the *document key* (sometimes referred to as the "document ID"). The key should be mapped to the unique identifier in your source data. The ability to uniquely identify specific search documents is required for retrieving a specific document in the search index, and for selective data processing at the per-document level.
67+
Every index requires one field that serves as the *document key* (sometimes referred to as the "document ID"). The key should be mapped to the unique identifier in your source data. The ability to uniquely identify specific search documents is required for retrieving a specific document in the search index, and for selective data processing at the per-document level.
6868

6969
1. Identify the fields in your data source that will contribute searchable content in the index. Searchable content includes short or long strings that are queried using the full text search engine. If the content is verbose (small phrases or bigger chunks), experiment with different analyzers to see how the text is tokenized.
7070

0 commit comments

Comments
 (0)