|
5 | 5 | ++++
|
6 | 6 |
|
7 | 7 | A data stream consists of one or more _backing indices_. Backing indices are
|
8 |
| -<<index-hidden,hidden>>, automatically-generated indices used to store a |
9 |
| -stream's documents. |
| 8 | +<<index-hidden,hidden>>, auto-generated indices used to store a stream's |
| 9 | +documents. |
10 | 10 |
|
11 | 11 | image::images/data-streams/data-streams-diagram.svg[align="center"]
|
12 | 12 |
|
@@ -78,10 +78,10 @@ You cannot add new documents to a stream's other backing indices, even by
|
78 | 78 | sending requests directly to the index. This means you cannot submit the
|
79 | 79 | following requests directly to any backing index except the write index:
|
80 | 80 |
|
81 |
| -* An <<docs-index_,Index API>> request with an |
| 81 | +* An <<docs-index_,index API>> request with an |
82 | 82 | <<docs-index-api-op_type,`op_type`>> of `create`. The `op_type` parameter
|
83 | 83 | defaults to `create` when adding new documents.
|
84 |
| -* A <<docs-bulk,Bulk API>> request using a `create` action |
| 84 | +* A <<docs-bulk,bulk API>> request using a `create` action |
85 | 85 |
|
86 | 86 | Because it's the only index capable of ingesting new documents, you cannot
|
87 | 87 | perform operations on a write index that might hinder indexing. These
|
@@ -124,17 +124,17 @@ cannot send update or deletion requests for existing documents to a data stream.
|
124 | 124 | To update or delete specific documents in a data stream, submit one of the
|
125 | 125 | following requests to the backing index containing the document:
|
126 | 126 |
|
127 |
| -* An <<docs-index_,Index API>> request with an |
| 127 | +* An <<docs-index_,index API>> request with an |
128 | 128 | <<docs-index-api-op_type,`op_type`>> of `index`.
|
129 | 129 | These requests must include valid <<optimistic-concurrency-control,`if_seq_no`
|
130 | 130 | and `if_primary_term`>> arguments.
|
131 | 131 |
|
132 |
| -* A <<docs-bulk,Bulk API>> request using the `delete`, `index`, or `update` |
| 132 | +* A <<docs-bulk,bulk API>> request using the `delete`, `index`, or `update` |
133 | 133 | action. If the action type is `index`, the action must include valid
|
134 | 134 | <<bulk-optimistic-concurrency-control,`if_seq_no` and `if_primary_term`>>
|
135 | 135 | arguments.
|
136 | 136 |
|
137 |
| -* A <<docs-delete,Delete API>> request |
| 137 | +* A <<docs-delete,delete API>> request |
138 | 138 |
|
139 | 139 | TIP: If you need to frequently update or delete existing documents across
|
140 | 140 | multiple indices, we recommend using an <<indices-add-alias,index alias>> and
|
|
0 commit comments